Actions
Bug #4859
closedA policy generation may occur when nothing has changed
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
We observe policy regeneration even when nothing changed.
This is due to a change in order of the node list in system variable (for managed nodes id and hostname) from run to run.
The relative order of the sequence is actually important so that managed (id, hostname) come at the same place.
So, we need to define a particular order for nodes, and be consistent on it from run to run.
Actions