User story #9305
closed
Document agent-server compatibility limits for 4.0
Added by Benoît PECCATTE about 8 years ago.
Updated about 8 years ago.
Description
As #6353 was merged, we need to document the consequences.
Short version: upgrade the server to 4.0 before upgrading the agents.
Long version: this is not always necessary, depending on options used ...
The consequences are:
- If not using skipidentify, this should be completely transparent for the user
- If using skipidentify, the user needs to upgrade the server before the nodes so that we move directly from (old agent, protocol v1) to (new agent, protocol v2) and we avoid the protocol v2 on client side + v1 promises on server side.
- Translation missing: en.field_tag_list set to Blocking 4.0
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-doc/pull/236
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Target version changed from 4.0.0~rc2 to 318
- Target version changed from 318 to 4.0.0~rc2
- Target version changed from 4.0.0~rc2 to 4.0.0~rc1
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by