OS Provisioning for VM did not finish in the allotted time
Issue
- The cluster creation process gets stuck in creating master nodes. The master creation process stays in the loop for around 40-45 mins. and then terminates with a timeout error.
- Azure requires the OS to provide a signal when it's booted and the machine is marked in provisioning until then. Since the control plane's ignition waits to get config from the bootstrap host, any failure where the machine-config-server on the bootstrap host cannot serve the ignition, it manifests in this error.
abc-oc.openshift - 2020-08-20 17:58:29,118 - ERROR - level=error msg="Error: Code=\"OSProvisioningTimedOut\" Message=\"OS Provisioning for VM 'vm-cluster-1234-master-2' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, make sure the image has been properly prepared (generalized).\\r\\n Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/ \\r\\n Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/ \\r\\n If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to shared image gallery. Please refer to https://aka.ms/movetosig for the same.\""
abc-oc.openshift - 2020-08-20 17:58:29,132 - CRITICAL - level=fatal msg="failed to fetch Cluster: failed to generate asset \"Cluster\": failed to create cluster: failed to apply using Terraform"
ERROR: Terminating execution on abc.commands.cmd_oc, Error: ["Exception: Exception while executing ['openshift-install', 'create', 'cluster', '--dir', '/<dir>', '--log-level=debug'] with ErrorCode: 1\n"]
Environment
- Red Hat OpenShift Container Platform
- 4.4.4 (Azure IPI)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.