Actions
Bug #23074
closed
Generation not queued when one already started
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Effort required:
Very Small
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Yes
Description
In ticket #22879 we change the state machine in place of just changing logs.
So now, we say that a generation is queued, when it is not.
Problem is that that line should not have been deleted: https://github.com/Normation/rudder/pull/4832/files#diff-2bfd5f67b4c377de308d2c78906f3ecf1684b561fc7c22739dfd18aea93156afL275
Workaround: start a generation by hand.
(still major because it breaks automation)
Updated by François ARMAND 10 months ago
- Related to Bug #22879: Too many "Policy Update Started" in event logs added
Updated by François ARMAND 10 months ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND 10 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/4896
Updated by François ARMAND 10 months ago
- Has duplicate Bug #23073: If a change is made while a policy generation is running, it does not always trigger a new policy generation when needed added
Updated by Anonymous 10 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|1cd552a57257c27d16ce9df8b70f16142b8fc292.
Updated by
Updated by Vincent MEMBRÉ 10 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.2.9 and 7.3.4 which were released today.
Actions