Bug #19248
closed
Empty /var/rudder/policy-generation-info/node-configuration-hashes.json after a policy generation that changed nothing
Added by Nicolas CHARLES over 3 years ago.
Updated about 3 years ago.
Category:
Web - Config management
Description
I had a policy generation that updated no nodes, and I ended up with an empty file
{"hashes": [
] }
it seems that the hashes are not correctly kept
- Status changed from New to In progress
- Assignee set to François ARMAND
- Assignee changed from François ARMAND to Nicolas CHARLES
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/3636
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request changed from https://github.com/Normation/rudder/pull/3636 to https://github.com/Normation/rudder/pull/3637
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.13 and 6.2.7 which were released today.
Also available in: Atom
PDF