-
Bug
-
Resolution: Done
-
Major
-
4.14.z, 4.16.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
In Progress
-
Bug Fix
-
Previously, control plane nodes created prior to OCP 4.12 would not have had the node-role.kubernetes.io/control-plane label. Now the MCO will add that label whenever it uncordons a control plane node if it was missing.
-
None
-
None
-
None
-
None
Description of problem:
IHAC who has IPI BM clusters initially installed on OpenShift 4.10 and upgraded to OpenShift 4.14 and 4.16; on these clusters that started from 4.10 the control-plane role does not exist, while on clusters installed on 4.14 both the master and control-plane roles are present.
Version-Release number of selected component (if applicable):
How reproducible:
When upgrade a cluster from OCP version 4.10 to OCP version 4.14 or 4.16
Steps to Reproduce:
1. Upgrade a cluster from OCP version 4.10 up to 4.12/4.14 or 14.6
2.
3.
Actual results:
After an upgrade like the above mentioned, OCP cluster on the version 4.14 or 4.16 have not any control-plane role in place
Expected results:
Afet the upgrade the cluster OCP will gain both roles, comprised control-plane role (so control-plane and master)
Additional info:
- depends on
-
OCPBUGS-63540 Need to label born in < 4.12 masters as control-plane
-
- Closed
-
- duplicates
-
OCPBUGS-63553 Need to label born in < 4.12 masters as control-plane
-
- Closed
-