Actions
Bug #11719
closed
Impossible to run in house CFEngine and Rudder agent side by side
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
If we have CFEngine installed, with up to date policies from the masterfiles (at least, newer than 3.6), and we install rudder-agent, policies from agent are erased
Indeed, check rudder agent checks for file /var/cfengine/inputs/common/1.0/update.cf , and if it's not there, it purges the promises, to replace by rudder initial promises
We need to have a finer detection of invalid files (most probably, check if policies in cfengine folder are distributed by Rudder, or managed by something else)
Updated by Nicolas CHARLES about 7 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES about 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-agent/pull/139
Updated by Nicolas CHARLES about 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-agent|a6217f8af7fec7ec249dd552ea6ee2858fbec1a2.
Updated by Vincent MEMBRÉ about 7 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.9 and 4.2.3 which were released today.
- 4.1.9: Announce Changelog
- 4.2.3: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Nicolas CHARLES over 6 years ago
- Related to Bug #12608: When a machine has both Rudder and CFEngine, rudder agent check counts CFEngine processes but acts on the Rudder service added
Actions