Bug #3908
closed
/etc/cron.d/rudder-agent is broken after launching cf-agent for the first time until a generation of promises by Rudder server
Added by Nicolas PERRON about 11 years ago.
Updated over 9 years ago.
Description
The generated cron file for rudder-agent has been fixed by #3894 and #3624 but the cron file in the initial promises is still wrong. Indeed, generation of promises with Rudder use String Template and needs to have a backslash before any 'and'.
Initial promises contains these backslash but are not generated by Rudder. We should remove them.
- Status changed from New to Pending technical review
- Assignee set to Nicolas CHARLES
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/180
- Status changed from Pending technical review to Pending release
Applied in changeset commit:0232ae93284d42ddaa6dd076645d6e591914542c.
Applied in changeset commit:7d086ff3e12b776f054ca77ed290c794fd5ebabd.
- Subject changed from The cron file in the initial promises is wrong with backslash before the 'and' and will install a wrong cron in /etc/cron.d/rudder-agent until a generation of promises to /etc/cron.d/rudder-agent is broken after launching cf-agent for the first time until a generation of promises by Rudder server
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.5, which was released today.
Check out:
- Project changed from 24 to Rudder
- Category set to Techniques
Also available in: Atom
PDF
Updated by Nicolas PERRON 
Updated by 
Updated by