Actions
Bug #19244
closedThere are 2 policy generation at each start of rudder policy server
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
One is triggered at every start, and one is caused by
INFO scheduled.job - Update in node inventories main information detected: triggering a policy generation
which happens during the current policy generation
it's not problemati, but that annoying
Actions