Bug #22646: We should initialize campaign service after plugin were added or else current events will be skipped (before being added again) - Rudder - Issue Tracker

Actions

Copy link

Bug #22646

closed

We should initialize campaign service after plugin were added or else current events will be skipped (before being added again)

Added by Félix DALLIDET over 1 year ago. Updated over 1 year ago.

Status:

Released

Priority:

N/A

Assignee:

Alexis Mousset

Category:

Web - Campaigns

Target version:

7.2.6

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

Major - prevents use of part of Rudder | no simple workaround

UX impact:

I hate Rudder for that

User visibility:

Getting started - demo | first install | Technique editor and level 1 Techniques

Effort required:

Priority:

118

Name check:

To do

Fix check:

To do

Regression:

Description

While working on the windows version of the plugin, the following error occurred after the campaigns were finished:

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

The event is tagged as "done", but no nodes are in its targets. The campaign did show the logs when it was running, and at least the "scheduling" reports were correct.
I can not see the result of the campaigns, which is very frustrating.

Files

campaign.png (146 KB) campaign.png

Félix DALLIDET, 2023-04-17 14:37

Subtasks

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Vincent MEMBRÉ over 1 year ago

Project changed from 92 to Rudder
Subject changed from could not translate into campaign of type system-update version 2 to We should initialize campaign service after plugin were added or else current events will be skipped (before being added again)
Target version deleted (~~7.3~~)