Actions
Bug #21418
closed
Campaign scheduler seems to not look for existing campaign at boot
Bug #21418:
Campaign scheduler seems to not look for existing campaign at boot
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
It seems that is a campaign exists in repo, but the next event was not already generated, then rudder does not generate it when it starts.
It looks like when the scheduler is inited, it misses a foreach(campaign in enabled campaigns) { check if next scheduled event is correct or if none, generates it}
See PR with the failing test
Updated by François ARMAND over 3 years ago
- Related to Architecture #21383: Add logic to handle campaign within Rudder added
Updated by François ARMAND over 3 years ago
- Assignee set to Vincent MEMBRÉ
Updated by François ARMAND over 3 years ago
- Status changed from New to In progress
- Assignee changed from Vincent MEMBRÉ to François ARMAND
Updated by François ARMAND over 3 years 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/4372
Updated by Vincent MEMBRÉ over 3 years ago
- Assignee changed from Vincent MEMBRÉ to François ARMAND
Updated by Anonymous over 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|4640945fb2bded2888bcfdbb11cbf12aa19aa3bb.
Updated by Vincent MEMBRÉ over 3 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.2.0~rc1 which was released today.
Actions