Actions
Bug #15863
closedVery often, a policy generation starts at rudder start, because of the flag file /opt/rudder/etc/policy-update-running
Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
i'm pretty sure that on most of my tests, there were no generation during restart of rudder
Actions