You can also submit product feedback to Azure community support. If you have questions or need help, create a support request, or ask Azure community support. The following example modifies the timeout value from 120 seconds to two seconds: sudo sed -i 's/maxwait=120/maxwait=2/g' $(locate DataSourceAzure.py) If you can't upgrade cloud-init to version 21.2 or a later version, you can edit the DataSourceAzure.py file to shorten the timeout value. resourcegroupname - (Required) The name of the Resource Group in which the Windows Virtual Machine. osdisk - (Required) A osdisk block as defined below. The first Network Interface ID in this list will be the Primary Network Interface on the Virtual Machine. Upgrade your copy of cloud-init to version 21.2 or a later version. A list of Network Interface IDs which should be attached to this Virtual Machine. The timeout interval for ephemeral disks is 120 seconds before the startup process continues. Because you're using an Azure VM that doesn't have local ephemeral disks, cloud-init must wait until the process times out. ![]() 19:35:50,481 - util.py: Failed partitioning operationĭevice /dev/disk/cloud/azure_resource did not exist and was not created with a udevadm settle.įile "/usr/lib/python3.6/site-packages/cloudinit/config/cc_disk_setup.py", line 141, in handleįile "/usr/lib/python3.6/site-packages/cloudinit/util.py", line 2292, in log_timeįile "/usr/lib/python3.6/site-packages/cloudinit/config/cc_disk_setup.py", line 780, in mkpartįile "/usr/lib/python3.6/site-packages/cloudinit/config/cc_disk_setup.py", lineĭuring VM startup, cloud-init runs the DataSourceAzure.py file in Python, and then waits for the local ephemeral disks ( /mnt/azure_resource) to become available. Messages:Dec 1 21:19:58 redhat84noephstor01 cloud-init: 21:19:58,531 - DataSourceAzure.py: ephemeral device '/dev/disk/cloud/azure_resource' did not appear after 120 seconds. Messages:Dec 1 19:35:50 redhat84noephstor01 cloud-init: 19:35:50,455 - DataSourceAzure.py: ephemeral device '/dev/disk/cloud/azure_resource' did not appear after 120 seconds. ![]() If you check log files such as /var/log/cloud-init.log and /var/log/waagent.log (init stage), you'll see output that resembles the following example: # grep "did not appear after 120 seconds" *Ĭloud-init.log: 19:35:50,455 - DataSourceAzure.py: ephemeral device '/dev/disk/cloud/azure_resource' did not appear after 120 seconds.Ĭloud-init.log: 21:19:58,531 - DataSourceAzure.py: ephemeral device '/dev/disk/cloud/azure_resource' did not appear after 120 seconds.Ĭloud-init-output.log: 19:35:50,455 - DataSourceAzure.py: ephemeral device '/dev/disk/cloud/azure_resource' did not appear after 120 seconds.Ĭloud-init-output.log: 21:19:58,531 - DataSourceAzure.py: ephemeral device '/dev/disk/cloud/azure_resource' did not appear after 120 seconds. Starting an Azure VM takes more than two minutes to finish on VM products that don't provide local ephemeral disks, such as the following products: ![]() This delay can cause a cloud-init-enabled Azure VM deployment to require more than two minutes (120 seconds) to start up. This article describes how to troubleshoot an unexpected startup delay on an Azure Virtual Machine (VM) that uses the cloud-init feature.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |