Actions
Bug #4634
closed
The script rudder-init.sh should not output CFEngine execution, and keep the output of all commands in the log
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
#3690 fixed this, but only on 2.7 and more, and not on 2.6
This is to backport the change in 2.6
Updated by Nicolas CHARLES about 10 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/267
Updated by Nicolas CHARLES about 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:f567b59448423a4bffe85bd0f752e0079fe4006c.
Updated by Jonathan CLARKE about 10 years ago
Applied in changeset commit:03f70c2b6dbaaf8cd17cd751fa2a461621d857db.
Updated by Nicolas CHARLES about 10 years ago
- Subject changed from The script rudder-init.sh should not output CFEngine execution to The script rudder-init.sh should not output CFEngine execution, and keep the output of all commands in the log
It also fixes the issue with the output of each component that overwrite the output log, rather than adding at its end
Updated by Vincent MEMBRÉ about 10 years ago
- Project changed from 34 to Rudder
- Category set to System integration
Updated by Vincent MEMBRÉ almost 10 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.
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions