Actions
Bug #22378
closedGenerate policies for campaigns before it starts officially, delete them after it stops (1 hour delay each)
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
We want to distribute campaign policies before they need to be applied so that they are correcly deployed before it needs, and keep them applied after offcial end of the campaign so that the node could still send reports if they reboot after.
EDIT: This is to handle problems that may arise in step 2 and 4 of scheduling management detailed in https://issues.rudder.io/issues/22130
Updated by Vincent MEMBRÉ over 1 year ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ over 1 year ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/4666
Updated by Alexis Mousset over 1 year ago
- Category set to Web - Config management
Updated by Vincent MEMBRÉ over 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|1e7f91b4e50abadd14d13b6d41922c97a436e6ea.
Updated by Vincent MEMBRÉ over 1 year ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 1 year ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.2.5 which was released today.
Actions