Red Hat Bugzilla – Bug 1463093
[WALA] VM status cannot become running if Provisioning.Enabled=n and Provisioning.UseCloudInit=n
Last modified: 2017-09-28 03:27:26 EDT
Description of problem:
When Provisioning.Enabled=n and Provisioning.UseCloudInit=n, the VM status cannot become running. It will keep "starting" for a long time and then failed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Prepare a VM in Azure. Set "Provisioning.Enabled=n" and "Provisioning.UseCloudInit=n" in /etc/waagent.conf
2. Deprovision this VM. Shutdown and capture as a generalized image. Then create a new VM base on it.
3. Wait for over 10 minutes. Check VM status from https://portal.azure.com
The VM status is always "Starting". And after a long time (about 1 hour) it becomes "Failed".
The VM status is "Running".
Root cause is when "Provisioning.Enabled=n" and "Provisioning.UseCloudInit=n", the wala skip the provisioning phase but not send "ready" report to Azure.(pa/provision/default.py Line#57-59)
Verified in WALA 2.2.18 upstream pre-release package. Will verify again in WALA-2.2.18-1 rpm package when it releases.