Project

General

Profile

Actions

User story #7906

closed

Create a migration script for inventory files from Rudder 2.11 to Rudder 3.2

Added by François ARMAND about 8 years ago. Updated over 7 years ago.

Status:
Released
Priority:
1
Category:
Scripts
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

As we don't have a migration path from 2.11 to 3.2, we took the decision to make an incompatible change in inventory file format from Rudder 2.11 to Rudder 3.2.
This is OK, since if someone upgrade from 2.11 to 3.0 or 3.1, and then to 3.2 (which are the only supported path), the file format evolution is compatible.

But in certain case, an user may want to upload inventory file produced by a Rudde 2.11 agent into a Rudder 3.2 server.

That won't work with the following kind of errors:

[2016-02-11 19:00:26] ERROR com.normation.inventory.provisioning.endpoint.FusionReportEndpoint - Error when trying to parse inventory 
<- Can't parse the input inventory, aborting 
<- Error when post processing report with 'post_process_inventory:check_consistency', abort 
<- Missing hostname tags (RUDDER∕HOSTNAME and OPERATINGSYSTEM/FQDN) in report. Having at least one of Those tags is mandatory.

So we need to have some script to transform 2.11 inventory file into 3.2. It may not work in certain case, but for the majority of them, it is quite easy to do.

Actions #1

Updated by François ARMAND about 8 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder-tools/pull/120
Actions #2

Updated by François ARMAND about 8 years ago

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

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from Pending release to Released
Actions

Also available in: Atom PDF