Worker machines not joining cluster after installing, or upgrading to, 4.14 OpenShift on Azure Stack Hub platform
Issue
- The problem occurs when installing OpenShift 4.14, or when upgrading from OpenShift 4.13 to 4.14, on Azure Stack Hub platform.
- When upgrading from 4.13 to 4.14 the installation will succeed, but the Cloud Controller Manager will report errors in its logs (see Diagnostic Steps section for details).
- When installing 4.14, worker nodes will fail to be added to the public load balancer, this will lead to the worker nodes not being added to the cluster, and the associated machine objects not being created.
- For new installations, the OpenShift console will not be available, nor will other workloads with load balancer type services that are exposed from worker nodes.
Environment
- Red Hat OpenShift Container Platform 4.13 and 4.14 on Azure Stack Hub
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.