Actions
Bug #2894
closedSome types are not handle by the eventlog migration from fileFormat2 to forFormat3
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Compliance & node report
Target version:
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.
Updated by Nicolas PERRON over 12 years ago
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Target version changed from 2.4.0~rc2 to 2.4.0~beta5
François will work on it for the beta5
Updated by François ARMAND over 12 years ago
- Status changed from New to In progress
Updated by François ARMAND over 12 years ago
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset 017434da91649d1da4a0fb77e851113f5ad5e60a.
Updated by Nicolas CHARLES over 12 years ago
- Status changed from Pending technical review to Released
This looks valid, and it removed code ! So it's great, thank you Francois
Actions