Actions
Bug #7176
closed
Unexpected reports on "cron daemon" component of system techniques
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
In the standard directives, the "CRON Deamon" reports, on my system, two lines:
http://i.imgur.com/H0snByf.jpg
It's unexpected so it's orange. In that case it should be green, I think.
it's also probably the same for other directives.
(rudder server 3.0.8, client 3.0.8 on Debian 7.8)
Updated by Nicolas CHARLES over 9 years ago
- Category set to System techniques
- Priority changed from N/A to 3
- Target version set to 3.0.9
This is obviously a bug in the system technique, that we should fix; unexpected should never happen
Thank you for the bug report !
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.0.9 to 3.0.10
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.0.10 to 3.0.11
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.0.11 to 3.0.12
Updated by Jonathan CLARKE about 9 years ago
- Subject changed from More than 1 report answer could be better interpreted to Unexpected reports on "cron daemon" component of system techniques
Updated by Jonathan CLARKE about 9 years ago
- Status changed from New to In progress
- Assignee set to Jonathan CLARKE
Updated by Jonathan CLARKE about 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/789
Updated by Jonathan CLARKE about 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-techniques|25dbc62339b8171eab1437b0b6d833a8060a3a43.
Updated by Benoît PECCATTE about 9 years ago
Applied in changeset rudder-techniques|5b570adf1203c4f68b30a4fcdf74231a8403d529.
Updated by Vincent MEMBRÉ about 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.12 and 3.1.5 which were released today.
- 3.0: Announce Changelog
- 3.1: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions