Project

General

Profile

Actions

Architecture #11155

closed

Warn on risk of updating file format

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

Status:
Released
Priority:
N/A
Category:
Documentation
Target version:
Effort required:
Name check:
Fix check:
Regression:

Description

We need to take care when updating fileFormat in the multi-site git sync scenario. See also https://www.rudder-project.org/redmine/issues/10899 for other problem related to that scenario.

The problem to take care of is when you have two rudder install: Rudder-dev (version y.a.b) and Rudder-prod (x.c.d), and you sync their git in the way: Rudder-dev ==> Rudder-prod (with an "archive restore" on Rudder2 after each git sync), then that scenario is broken if for version y, fileFormat is greater than in version x because rudder-prod will see a file format that it does not understand and will fail the archive restoration.

Actions #1

Updated by François ARMAND over 6 years ago

  • Description updated (diff)
  • Category set to Documentation
  • Status changed from New to In progress
  • Assignee set to François ARMAND
  • Target version set to 3.1.22

For now, we just want to add a comment with a link to that ticket in the corresponding code.

Actions #2

Updated by François ARMAND over 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/1703
Actions #3

Updated by François ARMAND over 6 years ago

  • Status changed from Pending technical review to Pending release
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.1.22, 4.1.6 and 4.2.0~beta3 which were released today.

Actions

Also available in: Atom PDF