Bug #2894: Some types are not handle by the eventlog migration from fileFormat2 to forFormat3 - Rudder - Issue Tracker

Actions

Copy link

Bug #2894

closed

Some types are not handle by the eventlog migration from fileFormat2 to forFormat3

Added by Nicolas PERRON about 12 years ago. Updated about 12 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

François ARMAND

Category:

Web - Compliance & node report

Target version:

2.4.0~beta5

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

It seems that some eventlog types are not handled by the migration since some groups and directives are still using "fileFormat=2":

# grep -R "fileFormat=\"2\"" /var/rudder/configuration-repository/directives/ | wc -l
47

# grep -R "fileFormat=\"2\"" /var/rudder/configuration-repository/groups/ | wc -l
5

and in the logs:

# cat /var/log/rudder/core/rudder-webapp.log | cut -d "]" -f 4- | sort | uniq 

 [type: ExportFullArchive]: no handler for that type.
 [type: ExportGroups]: no handler for that type.
 [type: ExportRules]: no handler for that type.
 [type: ExportTechniqueLibrary]: no handler for that type.
 [type: ImportFullArchive]: no handler for that type.
 [type: ImportGroups]: no handler for that type.
 [type: ImportRules]: no handler for that type.
 [type: ImportTechniqueLibrary]: no handler for that type.
 [type: ReloadTechniqueLibrary]: no handler for that type.
 [type: SuccessfulDeployment]: no handler for that type.