Project

General

Profile

Actions

Bug #6001

closed

Change request are not migrated to fileformat 6

Added by François ARMAND over 6 years ago. Updated over 6 years ago.

Status:
Released
Priority:
1
Category:
Web - Config management
Target version:
Severity:
User visibility:
Effort required:
Priority:

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).


Related issues

Related to Rudder - Architecture #9202: Clean old fileFormat migration and fileFormat numbering policyReleasedVincent MEMBRÉ2016-10-03Actions
Actions #1

Updated by François ARMAND over 6 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
Actions #2

Updated by François ARMAND over 6 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #4

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.0~beta2, which were these days.

Actions #5

Updated by François ARMAND over 4 years ago

  • Related to Architecture #9202: Clean old fileFormat migration and fileFormat numbering policy added
Actions

Also available in: Atom PDF