Scaling up a new node failing with `OSProvisioningTimedOut` on Azure IPI RHOCP 4
Issue
- Scaling up a new node failing with the following error in Azure console
Failed
node.example.com
Additional error information is available for this virtual machine:
GENERAL
Provisioning state Provisioning failed.
OS Provisioning for VM 'node.example.com' 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).
* Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/
* Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/
* 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..
OSProvisioningTimedOut
Provisioning state error code ProvisioningState/failed/OSProvisioningTimedOut
Guest agent Not Ready.
VM status blob is found but not yet populated.
DISKS
node.example.com_OSDisk Provisioning succeeded.
Virtual machine in a failed state?
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
- Azure IPI
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.