Actions
Bug #22139
closedRunning deleted campaign don't get their directive cleaned-up
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
If a campaign is deleted when it was running (and so, the directive/rule were created), then the configuration elements are not cleaned up.
Then, if you try to create a new campaign with the same name, you get an infinite log that kill the server/fill the disks:
[2022-11-25 16:10:08+0000] ERROR campaign - Inconsistency: Cannot set directive with name ' #1' : this name is already in use.
(yes, name was empty, because I didn't noticed I forgot to put one both time)
Workaround: delete the new campaign, then create one with a different name.
Solution: directive/rule of a running event must be deleted if the campaign is deleted (and a generation triggered).
Bonus: make name mandatory for campaign.
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.2.3 to 7.2.4
Updated by Vincent MEMBRÉ almost 2 years ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
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/4627
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 7.2.4 to 7.2.5
Updated by Vincent MEMBRÉ almost 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|4b6f935326972f7241f30852da2419ae573fb20f.
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 7.2.5 to 7.2.4
Updated by Vincent MEMBRÉ almost 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.2.4 which was released today.
Actions