Project

General

Profile

Actions
Copy link

Bug #22378

closed

Generate policies for campaigns before it starts officially, delete them after it stops (1 hour delay each)

Added by Vincent MEMBRÉ almost 2 years ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Config management
Target version:
7.2.5
Pull Request:
https://github.com/Normation/rudder/p...
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

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ almost 2 years ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ almost 2 years 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
Actions
Copy link
 #3

Updated by Alexis Mousset almost 2 years ago

  • Category set to Web - Config management
Actions
Copy link
 #5

Updated by François ARMAND almost 2 years ago

  • Description updated (diff)
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ almost 2 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 1 year ago

  • Fix check changed from To do to Checked
Actions
Copy link
 #8

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
Copy link

Also available in: Atom PDF