New node fail to add provisioning/provisioned node to OCP cluster running in Azure
Issue
- While increasing the machineset count the machine provisions but the node never gets added to the cluster.
- New node fail to add provisioning/provisioned node to cluster running in Azure
Jan 16 18:04:00 new-machine-worker-name sh[3401]: Error: error pulling image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:dda511a05e243ac922b29b29de99f347cab19088a1c95222f196dd5c9c1502bc": unable to pull quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:dda511a05e243ac922b29b29de99f347cab19088a1c95222f196dd5c9c1502bc: unable to pull image: Error initializing source docker://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:dda511a05e243ac922b29b29de99f347cab19088a1c95222f196dd5c9c1502bc: error pinging docker registry quay.io: Get https://quay.io/v2/: dial tcp ip:443: i/o timeout
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
- Azure
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.