-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.12.z
-
+
-
Yes
-
MCO Sprint 232
-
1
-
Rejected
-
False
-
-
-
Bug Fix
-
Done
Description of problem:
When attempting to add nodes to a long-lived 4.12.3 cluster, net new nodes are not able to join the cluster. They are provisioned in the cloud provider (AWS), but never actually join as a node.
Version-Release number of selected component (if applicable):
4.12.3
How reproducible:
Consistent
Steps to Reproduce:
1. On a long lived cluster, add a new machineset
Actual results:
Machines reach "Provisioned" but don't join the cluster
Expected results:
Machines join cluster as nodes
Additional info:
- blocks
-
OCPBUGS-10220 Newly provisioned machines unable to join cluster
- Closed
- is blocked by
-
MCO-519 Impact Old AWS boot images vs. 4.12: aws-kubelet-providerid and aws-kubelet-nodename
- Closed
- is cloned by
-
OCPBUGS-10220 Newly provisioned machines unable to join cluster
- Closed
- is related to
-
OCPBUGS-9969 4.1 born cluster fails to scale-up due to podman run missing `--authfile` flag
- Closed
- links to
-
RHSA-2023:5006 OpenShift Container Platform 4.14.z security update