Project

General

Profile

Actions
Copy link

Bug #12398

closed

When upgrading from 4.1 to 4.3, reports from Rudder Techniques break reporting

Added by Nicolas CHARLES about 6 years ago. Updated about 6 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Techniques
Target version:
4.3.0
Pull Request:
https://github.com/Normation/ncf/pull...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

I upgraded from 4.1 to 4.3, with a Directive based on "Packages" Technique
I did not upgrade the Technique (I first wanted to check that everything was fine) - however it turned out I had no more reports

Indeed, I have the following lines generated

R: @@packageManagement@@log_info@@32377fd7-02fd-43d0-aab7-28460a91347b@@bd5e5855-0ac1-4061-bd56-5f974c59f181@@0@@@@@@2018-04-10 13:45:57+00:00##root@#Presence of package vim-enhanced in any version was correct

with the postgresql error

STATEMENT:  insert into RudderSysEvents (executionDate, nodeId, ruleId, directiveId, serial, Component, KeyValue, executionTimeStamp, eventType, msg, Policy) values ('2018-04-10T13:35:31.363543+00:00','root', '32377fd7-02fd-43d0-aab7-28460a91347b' , 'bd5e5855-0ac1-4061-bd56-5f974c59f181', '0', '', '', '2018-04-10 13:35:29+00:00', 'log_info', 'Presence of package vim-enhanced in any version was correct', '' )
ERROR:  new row for relation "ruddersysevents" violates check constraint "ruddersysevents_component_check"

this may also happen with others techniques

Actions
Copy link

Also available in: Atom PDF