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 over 10 years ago.
Updated about 9 years ago.
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
- Status changed from New to Pending technical review
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-doc/pull/30
- Status changed from Pending technical review to Pending release
Applied in changeset commit:76b648a9f0e9236c21625b7891fc8c51980406b6.
Applied in changeset commit:d14b146817824da15b6f8d22725443b6bef43ead.
- Status changed from Pending release to Pending technical review
- Pull Request changed from https://github.com/Normation/rudder-doc/pull/30 to https://github.com/Normation/rudder-doc/pull/32
- Status changed from Pending technical review to Pending release
Applied in changeset commit:a271bef511330d2de31577e8fcabffd093955306.
Applied in changeset commit:e449f5c5d1ecced6e8269168dd57a79e04103fff.
- Tracker changed from Bug to Enhancement
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.8.0~beta1, which was released today.
Check out:
- Category set to Documentation
- Tracker changed from Enhancement to User story
Also available in: Atom
PDF
Updated by Nicolas PERRON 
Updated by 
Updated by 
Updated by