Architecture #10718
closed
Rudder 3.1 agents will not be compatible with Rudder >=4.3
Added by Alexis Mousset almost 7 years ago.
Updated about 6 years ago.
Description
Direct upgrade from 3.1 to >4.1 will not be possible, and the upgrade path will include an upgrade to 4.1 first.
This is compatible with our support policy as 4.1 will be the next ESR and is fully compatible with Rudder 3.1 agents.
This means:
- Remove legacy package promises from system techniques
- Remove old acl based on IP/hostname
- Disable the old protocol on the server
- Remove the "skipidentify" setting from the webapp as it is now ignored
And also:
- Drop CFEngine 3.6 support in the new ncf branch
- Synchronize the CFEngine stdlib that will now be compatible with ncf
- Target version changed from 4.2.0~beta1 to 4.2.0~beta2
- Target version changed from 4.2.0~beta2 to 4.2.0~beta3
- Target version changed from 4.2.0~beta3 to 4.2.0~rc1
- Target version changed from 4.2.0~rc1 to 4.2.0~rc2
- Target version changed from 4.2.0~rc2 to 4.2.0
- Target version changed from 4.2.0 to 4.2.1
- Target version changed from 4.2.1 to 4.2.2
- Subject changed from Rudder 3.1 agents will not be compatible with Rudder >4.1 to Rudder 3.1 agents will not be compatible with Rudder >4.2
- Target version changed from 4.2.2 to 4.3.0~beta1
- Subject changed from Rudder 3.1 agents will not be compatible with Rudder >4.2 to Rudder 3.1 agents will not be compatible with Rudder >4.3
- Subject changed from Rudder 3.1 agents will not be compatible with Rudder >4.3 to Rudder 3.1 agents will not be compatible with Rudder >=4.3
- Status changed from New to Rejected
Also available in: Atom
PDF
Updated by 
Updated by