Project

General

Profile

Actions
Copy link

Bug #23074

closed

Generation not queued when one already started

Added by François ARMAND over 1 year ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
-
Target version:
7.2.9
Pull Request:
https://github.com/Normation/rudder/p...
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)

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #22879: Too many "Policy Update Started" in event logsReleasedNicolas CHARLESActions
Has duplicate Rudder - Bug #23073: If a change is made while a policy generation is running, it does not always trigger a new policy generation when neededRejectedActions
Actions
Copy link

Also available in: Atom PDF