Bug #24441
closed
Cannot translate campaign on boot, leading to skipped events
Added by Michel BOUISSOU 8 months ago.
Updated 8 months ago.
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
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
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 »
- 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
I was fixed in #22646 but was reintroduced by upmerge ...
- Project changed from 92 to Rudder
- Target version changed from 7.3 to 7.3.14
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Maybe it was reintroduced in #23727 which restarted mainCampaignService when unwanted
- 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
- Related to Architecture #23727: Group all node related access into one NodeFactRepository added
- Target version changed from 7.3.14 to 8.1.0~beta2
Definetely reintroduced in 8.1 alpha1
- Subject changed from Cannot translate campaign on boot to Cannot translate campaign on boot, leading to skipped events
- 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
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.1.0~beta2 which was released today.
Also available in: Atom
PDF