Actions
Bug #19248
closedEmpty /var/rudder/policy-generation-info/node-configuration-hashes.json after a policy generation that changed nothing
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
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
Updated by François ARMAND over 3 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by Nicolas CHARLES over 3 years ago
- Assignee changed from François ARMAND to Nicolas CHARLES
Updated by Nicolas CHARLES over 3 years ago
- 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
Updated by François ARMAND over 3 years ago
- 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
Updated by François ARMAND over 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|1a5107881e06b65dd0935dc625a78ff9d69b6b2a.
Updated by Nicolas CHARLES over 3 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 3 years ago
- 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.
Actions