Project

General

Profile

Actions

Bug #4761

closed

Reports are not inserted into Rudder because regexp in rsyslog is too greedy when matching execuction timestamp

Added by Vincent MEMBRÉ almost 9 years ago. Updated over 8 years ago.

Status:
Released
Priority:
1
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

Whe saw from bug #4431 that regexp from rsyslog does not match data correctly from reports

But #4431 only updates the initial promises, we need to add this fix in the technique too


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #4431: The rsyslog regexp matching executionTimeStamp is too greedy and could take more characters than it shouldReleasedNicolas CHARLES2014-01-31Actions
Actions #1

Updated by Vincent MEMBRÉ almost 9 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to Jonathan CLARKE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/345
Actions #2

Updated by Vincent MEMBRÉ almost 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset policy-templates:commit:dd173ea7aa23de6bcc7acd3336a8cc4378a52d9c.

Actions #3

Updated by Jonathan CLARKE almost 9 years ago

Applied in changeset policy-templates:commit:80efecaa0f6d8ba513c1b3704b8089aaa432af29.

Actions #4

Updated by Vincent MEMBRÉ over 8 years ago

  • Subject changed from Regexp in rsyslog is too greedy when matching execuction timestamp on reports to Reports are not inserted into Rudder because regexp in rsyslog is too greedy when matching execuction timestamp
Actions #5

Updated by Vincent MEMBRÉ over 8 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.6.13 (announcement , changelog), 2.9.5 (announcement , changelog) and 2.10.1 (announcement , changelog), which were released today.

Actions

Also available in: Atom PDF