Actions
Bug #6001
closed
Change request are not migrated to fileformat 6
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
If change requests were created with a Rudder version before 3.0, when we try to read them with Rudder 3.0 we are getting:
[2014-12-15 14:16:33] ERROR com.normation.rudder.repository.jdbc.ChangeRequestsMapper - Error when trying to get the content of the change request 2 : Failure(Bad fileFormat (expecting 6): <changeRequest fileFormat="5"><groups/><directives/><rules>...</rules><globalParameters/></changeRequest>,Empty,Empty)There seems to be missing the part about change request in /rudder-core/src/main/scala/com/normation/rudder/migration/XmlFileFormatMigration_5_6.scala (look for ChangeRequestsMigration_4_5 in /rudder-core/src/main/scala/com/normation/rudder/migration/XmlFileFormatMigration_4_5.scala for comparison).
Updated by François ARMAND about 10 years ago
- Status changed from 8 to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/726
Updated by François ARMAND about 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset c4f7793c0e08573a8a12c5b41d7021bd8e0022c0.
Updated by Nicolas CHARLES about 10 years ago
Applied in changeset 79e945a2e8317594504b76a2db112d408615fbd6.
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta2, which were these days.
- Announcement 3.0
- Changelog 3.0
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by François ARMAND about 8 years ago
- Related to Architecture #9202: Clean old fileFormat migration and fileFormat numbering policy added
Actions