Architecture #9207
closed
Transient policy error after upgrade, need to improve handling of policies update during server upgrade (rudder-upgrade vs. ncf vs. rudder-techniques)
Added by Alexis Mousset about 8 years ago.
Updated over 3 years ago.
Description
On the server, we upgrade different packages when updating Rudder, particularly the system techniques in Rudder techniques, the ncf sources in the ncf package, and rudder-webapp which start the rudder-upgrade script which updates the policy
We need a way to avoid transient errors like #8792 or #9171 and to avoid doing the update in a random order, with a transient broken state.
- Related to Bug #8792: Transient ncf error when updating from 3.1.10 to 3.1.12 added
- Related to Bug #9171: Broken run on 3.2 after 3.1 upgrade added
- Tracker changed from User story to Bug
- Subject changed from Improve handling of policies update during server upgrade (rudder-upgrade vs. ncf vs. rudder-techniques) to Policy loading error after upgrade, need to mprove handling of policies update during server upgrade (rudder-upgrade vs. ncf vs. rudder-techniques)
- Reproduced set to No
- Related to Bug #8710: Cannot read ncf inputs due to duplicated path added
- Related to Bug #9416: Transient error during upgrade from 3.1 to 4.0 added
- Subject changed from Policy loading error after upgrade, need to mprove handling of policies update during server upgrade (rudder-upgrade vs. ncf vs. rudder-techniques) to Transient policy error after upgrade, need to improve handling of policies update during server upgrade (rudder-upgrade vs. ncf vs. rudder-techniques)
- Related to Bug #10028: Transient update error on ncf/local added
Alexis, can you elaborate on what the bug is and what the consequences are ?
The consequences are transient broken policies on the server, possibly distributed to nodes.
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Tracker changed from Bug to Architecture
- Related to Bug #11128: error: Fatal CFEngine error: Augment scope, formal and actual parameter mismatch is fatal added
- Has duplicate Bug #9179: Error when restarting rudder-agent during upgrade added
- Related to Bug #12223: Transient policy generation error at upgrade from 4.2 to 4.3 added
This should be fixed in 5.1 by the package merge that will allow (more) atomic upgrades.
- Status changed from New to Resolved
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by