-
Bug
-
Resolution: Done-Errata
-
Minor
-
4.11.z
Description of problem:
When using canary rollout, paused MCPs begin updating when the user triggers the cluster update.
Version-Release number of selected component (if applicable):
How reproducible:
Approximately 3/10 times that I have witnessed.
Steps to Reproduce:
1. Install cluster 2. Follow canary rollout strategy: https://docs.openshift.com/container-platform/4.11/updating/update-using-custom-machine-config-pools.html 3. Start cluster update
Actual results:
Worker nodes in paused MCPs begin update
Expected results:
Worker nodes in paused MCPs will not begin update until cluster admin unpauses the MCPs
Additional info:
This has occurred with my customer in their Azure self-managed cluster and their on-prem cluster in vSphere, as well as my lab cluster in vSphere.
- blocks
-
OCPBUGS-31839 [release-4.15] When starting cluster update, nodes in paused MCPs begin updating
- Closed
- is cloned by
-
OCPBUGS-31839 [release-4.15] When starting cluster update, nodes in paused MCPs begin updating
- Closed
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update