Project

General

Profile

Actions
Copy link

Bug #24441

closed

Cannot translate campaign on boot, leading to skipped events

Bug #24441: Cannot translate campaign on boot, leading to skipped events

Added by Michel BOUISSOU almost 2 years ago. Updated almost 2 years ago.

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

Download all 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
Campaign_inconsistency_240314a.png
Campaign_inconsistency_240314b.png

Related issues 2 (0 open — 2 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
Copy link

Also available in: PDF Atom