Project

General

Profile

Actions

Bug #21418

closed

Campaign scheduler seems to not look for existing campaign at boot

Added by François ARMAND 7 months ago. Updated 5 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Campaigns
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
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


Related issues 1 (0 open1 closed)

Related to Rudder - Architecture #21383: Add logic to handle campaign within RudderReleasedFrançois ARMANDActions
Actions #1

Updated by François ARMAND 7 months ago

Actions #2

Updated by François ARMAND 7 months ago

  • Assignee set to Vincent MEMBRÉ
Actions #3

Updated by François ARMAND 7 months ago

  • Status changed from New to In progress
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
Actions #4

Updated by François ARMAND 7 months 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
Actions #5

Updated by Vincent MEMBRÉ 7 months ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND
Actions #6

Updated by Anonymous 7 months ago

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

Updated by Vincent MEMBRÉ 5 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 7.2.0~rc1 which was released today.

Actions

Also available in: Atom PDF