-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.19.z, 4.20.z, 4.21.0
-
Quality / Stability / Reliability
-
False
-
-
5
-
Moderate
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
In the MCN object, spec.configVersion.desired is being set after an update completes its update prepared phase and status.configVersion.desired is set. This is the opposite of what is intended functionality.
Version-Release number of selected component (if applicable):
Observed in 4.19, 4.16, and 4.15, so presumably in all versions with MCN in tech preview (4.15+)
How reproducible:
Always
Steps to Reproduce:
1. Start a 4.19 cluster with tech preview enabled. 2. Apply a MC. 3. Carefully watch the MCN config versions update. Example command to follow relevant fields: oc describe machineconfignode/ip-10-0-108-23.ec2.internal | grep -E "Config Version|UpdatePrepared" -A 2
Actual results:
In this case, `rendered-worker-aa4a179eba20c0a02b402a34587d27a1` represents the old rendered config and `rendered-worker-25fcd6bb6fc89837a77955fcd30ce025` represents the new rendered config. The following shows how the MCN object updates during the upgrade process:
Before the update:
Spec: Config Version: Desired: rendered-worker-aa4a179eba20c0a02b402a34587d27a1 … Status: Conditions: Message: This node has not yet entered the UpdatePrepared phase Reason: NotYetOccured Status: False Type: UpdatePrepared Last Transition Time: 2025-03-04T14:05:24Z … Config Version: Current: rendered-worker-aa4a179eba20c0a02b402a34587d27a1 Desired: rendered-worker-aa4a179eba20c0a02b402a34587d27a1
Update is preparing:
Spec: Config Version: Desired: rendered-worker-aa4a179eba20c0a02b402a34587d27a1 … Status: Conditions: Message: This node has not yet entered the UpdatePrepared phase Reason: NotYetOccured Status: False Type: UpdatePrepared … Config Version: Current: rendered-worker-aa4a179eba20c0a02b402a34587d27a1 Desired: rendered-worker-25fcd6bb6fc89837a77955fcd30ce025
Update is prepared:
Spec: Config Version: Desired: rendered-worker-25fcd6bb6fc89837a77955fcd30ce025 … Status: Conditions: Message: Update is Compatible. Reason: UpdateCompatible Status: True Type: UpdatePrepared … Config Version: Current: rendered-worker-aa4a179eba20c0a02b402a34587d27a1 Desired: rendered-worker-25fcd6bb6fc89837a77955fcd30ce025
Expected results:
The spec.configVersion.desired value should immediately be set when the node annotation is updated on the node. Later, after the update is validated, the status.configVersion.desired value should be set. These values are being set out of order.
Additional info:
- blocks
-
OCPBUGS-59766 Desired config version in MCN is being set in status before spec
-
- New
-
- causes
-
OCPBUGS-59776 Machine-Config-Updater causes too many applies in techpreview tests
-
- Verified
-
- is blocked by
-
MCO-1501 Support Custom MCPs in MCN
-
- Closed
-
- is cloned by
-
OCPBUGS-59766 Desired config version in MCN is being set in status before spec
-
- New
-
- links to
(2 links to)