Project

General

Profile

Bug #4088

Error when upgrading from a Rudder server 2.3 if both policy.xml and metadata.xml were existing for the same techniques

Added by Vincent MEMBRÉ over 6 years ago. Updated over 6 years ago.

Status:
Released
Priority:
4
Category:
-
Target version:
Pull Request:
Severity:
User visibility:
Effort required:
Priority:

Description

A long time ago, we used to have some policy.xml files instead of metadata.xml for our techniques.

This old remains from 2.3 blocked one of my upgrade:

techniques rpmPackageInstallation version 3.0 and 3.1 were having both policy.xml and metadata.xml.

the upgrade process looks for policy.xml files, and tries to transform them into metadata.xml, which leads to an error if metadata.xml already exists.

removing the policy.xml files make the upgrade process works.

the upgrade process should not fail is metadata.xml already exists but only delete the policy.xml file while warning you that metadata.xml was already existing.

#1

Updated by Matthieu CERDA over 6 years ago

  • Status changed from New to In progress
  • Assignee changed from Vincent MEMBRÉ to Matthieu CERDA

Grabbin' this !

#2

Updated by Matthieu CERDA over 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Matthieu CERDA to Jonathan CLARKE
  • % Done changed from 0 to 100

PR available: https://github.com/Normation/rudder-packages/pull/166

I decided to go with the "force move" approach because no policy.xml should subsist this way.

#3

Updated by Matthieu CERDA over 6 years ago

  • Status changed from Pending technical review to Pending release

Applied in changeset packages:commit:9802fec1362799fa383bcf0e69c2a87eb2e7fd20.

#4

Updated by Jonathan CLARKE over 6 years ago

Applied in changeset packages:commit:c98e91b5ec777edb874669fecdb54e55a6225716.

#5

Updated by Nicolas PERRON over 6 years ago

  • Subject changed from Error when upgrading a server where both policy.xml and metadata.xml were existing for the same techniques to Error when upgrading from a Rudder server 2.3 if both policy.xml and metadata.xml were existing for the same techniques
#6

Updated by Nicolas PERRON over 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.4.12 which was released today.
Check out:

Also available in: Atom PDF