-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
4.14.z
-
No
-
False
-
Description of problem:
~|⇒ oc get clusterversion oc gNAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.14.16 True False 3d1h Cluster version is 4.14.16 ~|⇒ oc get no NAME STATUS ROLES AGE VERSION ip-10-31-76-114.aws6.cloud.xyz.org Ready worker 3d v1.27.10+c79e5e2 ip-10-31-76-126.us-west-2.compute.internal Ready worker 128d v1.27.10+c79e5e2 ip-10-31-76-155.us-west-2.compute.internal Ready worker 192d v1.27.10+c79e5e2 ip-10-31-76-211.us-west-2.compute.internal Ready worker 29d v1.27.10+c79e5e2 ip-10-31-78-203.aws6.cloud.xyz.org Ready worker 3d v1.27.10+c79e5e2 ip-10-31-79-170.aws6.cloud.xyz.org Ready worker 2d19h v1.27.10+c79e5e2 ip-10-31-80-163.aws6.cloud.xyz.org Ready worker 2d23h v1.27.10+c79e5e2 ip-10-31-80-251.us-west-2.compute.internal Ready worker 2y59d v1.27.10+c79e5e2
Version-Release number of selected component (if applicable):
4.14.16
How reproducible:
All newly added nodes since the upgrade
Steps to Reproduce:
1. Successful uggrade 4.14.16 2. Scale up new nodes 3. New nodes have incorrect nodename / hostname
Actual results:
Wrong hostname
Expected results:
Consistent hostname
Additional info: