Project

General

Profile

Actions
Copy link

User story #3987

closed

User story #3986: Add informations about the upgrade process for Rudder 2.8

Update documentation about the upgrade process for Rudder 2.8

Added by Nicolas PERRON about 11 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
Documentation
Target version:
2.8.0~beta1
Pull Request:
https://github.com/Normation/rudder-d...
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

As said in #3871, the upgrade process for Rudder 2.8 should follow this:

The upgrade process should be, for 2.8 specifically:
  • Make sure the Rudder server to be upgraded is in a version that is at least 2.4.9, 2.6.6 and 2.7.3 before attempting to upgrade to 2.8.*
  • Ensure that all nodes' promises have been regenerated since the server upgrade to this version (do we do this automatically on package upgrade now? if so, ignore, if not explain how to do it)
  • Upgrade all agents connected to that server to 2.8.*
  • Upgrade the Rudder server to 2.8
Actions
Copy link

Also available in: Atom PDF