Bug #4431
closed
The rsyslog regexp matching executionTimeStamp is too greedy and could take more characters than it should
Added by Nicolas PERRON almost 11 years ago.
Updated over 10 years ago.
Category:
Web - Compliance & node report
Description
Rsyslog regular expression is not enough precise for the executionTimeStamp part which could take extra characters not related to the timestamp.
- Status changed from New to Pending technical review
- Assignee set to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/279
- Status changed from Pending technical review to Discussion
- Assignee changed from Jonathan CLARKE to Nicolas PERRON
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
- Status changed from Discussion to Pending technical review
Nicolas updated the pull request, swithcing back to technical review!!
- Assignee changed from Jonathan CLARKE to Nicolas CHARLES
- Status changed from Pending technical review to Pending release
Applied in changeset commit:6c7a8447a1f5716c43a5cf3ff54567c98b7b84d1.
Applied in changeset commit:6bdbe00ecc2958f276dd1176b573b7e8a90309a3.
- Subject changed from The rsyslog regular expression matching executionTimeStamp into vimRudder reports is too greedy and could take more characters than it should to The rsyslog regexp matching executionTimeStamp is too greedy and could take more characters than it should
- Project changed from 24 to Rudder
- Category set to Web - Compliance & node report
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.11, which was released today.
Check out:
Also available in: Atom
PDF
Updated by Nicolas PERRON 
Updated by Jonathan CLARKE 
Updated by