-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.18
-
Important
-
None
-
3
-
MCO Sprint 261, MCO Sprint 262
-
2
-
Proposed
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
When we create a MOSC to enable OCL in a pool, and then we delete the MOSC resource to revert it, then the MOSB and CMs are garbage collected but we need to wait a long and random time until the nodes are updated with the new config.
Version-Release number of selected component (if applicable):
$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.18.0-0.test-2024-10-15-080246-ci-ln-0gsqflb-latest True False 8h Cluster version is 4.18.0-0.test-2024-10-15-080246-ci-ln-0gsqflb-latest
How reproducible:
Always
Steps to Reproduce:
1. Create a MOSC to enable OCL in the worker pool 2. Wait until the new OCL image is applied to all worker nodes 3. Remove the MOSC resource created in step 1
Actual results:
MOSB and CMs are cleaned, but the nodes are not updated. After a random amount of time the nodes are updated. (Somewhere around 10-20 minutes)
Expected results:
There should be no long pause between the deletion of the MOSC resource and the beginning of the nodes update process.
Additional info:
As a workaround, if we add any label to the worker pool to force a sync operation the worker nodes start updating immediately.
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update