Project

General

Profile

Actions

Bug #24441

closed

Cannot translate campaign on boot, leading to skipped events

Added by Michel BOUISSOU about 2 months ago. Updated about 1 month ago.

Status:
Released
Priority:
N/A
Category:
-
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

A system update campaign created with Rudder 8.1 beta 2 nightly on 2024/3/13 displays the following error after server has been rebooted.

This event will be skipped. Reason: An error occurred when processing event: Inconsistency: could not translate into campaign of type system-update version 2

(See screenshot)


Files

Campaign_inconsistency_240314a.png (74.3 KB) Campaign_inconsistency_240314a.png Error message Michel BOUISSOU, 2024-03-14 09:05
Campaign_inconsistency_240314b.png (27.4 KB) Campaign_inconsistency_240314b.png Other error message Michel BOUISSOU, 2024-03-14 09:15

Related issues 2 (0 open2 closed)

Related to Rudder - Bug #22646: We should initialize campaign service after plugin were added or else current events will be skipped (before being added again)ReleasedAlexis MoussetActions
Related to Rudder - Architecture #23727: Group all node related access into one NodeFactRepositoryReleasedVincent MEMBRÉActions
Actions #2

Updated by Michel BOUISSOU about 2 months ago

Another, different error message that appears one one of the “multiplied clones” of this campaign (see #24442)

« This event will be skipped. Reason: An error occurred when processing event: Unexpected: System directive 'One shot Linux upgrade #2 [cbaead8d-c8c8-4d39-8db3-d337e8582f19/15a7905c-2993-40bc-a111-2a6a4d240310]' (15a7905c-2993-40bc-a111-2a6a4d240310) can't be updated »

Actions #3

Updated by Vincent MEMBRÉ about 2 months ago

  • Subject changed from Rudder 8.1 beta 2 - Inconsistency: could not translate into campaign of type system-update version 2 to Cannot translate campaign on boot
  • Target version changed from 8.1 to 7.3

It's more probably a bug in Rudder core, and i think it was already reported

Actions #4

Updated by Vincent MEMBRÉ about 1 month ago

I was fixed in #22646 but was reintroduced by upmerge ...

Actions #5

Updated by Vincent MEMBRÉ about 1 month ago

  • Project changed from 92 to Rudder
  • Target version changed from 7.3 to 7.3.14
Actions #6

Updated by Vincent MEMBRÉ about 1 month ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
Actions #7

Updated by Vincent MEMBRÉ about 1 month ago

Maybe it was reintroduced in #23727 which restarted mainCampaignService when unwanted

Actions #8

Updated by Vincent MEMBRÉ about 1 month ago

  • Related to Bug #22646: We should initialize campaign service after plugin were added or else current events will be skipped (before being added again) added
Actions #9

Updated by Vincent MEMBRÉ about 1 month ago

  • Related to Architecture #23727: Group all node related access into one NodeFactRepository added
Actions #10

Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 7.3.14 to 8.1.0~beta2

Definetely reintroduced in 8.1 alpha1

Actions #11

Updated by Vincent MEMBRÉ about 1 month ago

  • Subject changed from Cannot translate campaign on boot to Cannot translate campaign on boot, leading to skipped events
Actions #12

Updated by Vincent MEMBRÉ about 1 month 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/5474
Actions #13

Updated by Anonymous about 1 month ago

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

Updated by Vincent MEMBRÉ about 1 month ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 8.1.0~beta2 which was released today.

Actions

Also available in: Atom PDF