diff options
author | Johnson Shi <Johnson.Shi@microsoft.com> | 2021-02-22 13:50:59 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-02-22 16:50:59 -0500 |
commit | a64b73808857fa7b4f262422ce2c87eedbce10d5 (patch) | |
tree | f31bbbb83562f5c021ca69d9999b30c85ced9852 /tests/integration_tests/bugs/test_lp1886531.py | |
parent | e384a5436560c9494118f0999c314982d4912d27 (diff) | |
download | vyos-cloud-init-a64b73808857fa7b4f262422ce2c87eedbce10d5.tar.gz vyos-cloud-init-a64b73808857fa7b4f262422ce2c87eedbce10d5.zip |
Azure: Support for VMs without ephemeral resource disks. (#800)
Changes:
* Only merge in default Azure cloud ephemeral disk configs
during DataSourceAzure._get_data() if the ephemeral disk
exists.
* DataSourceAzure.address_ephemeral_resize() (which is
invoked in DataSourceAzure.activate() should only set up
the ephemeral disk if the disk exists.
Azure VMs may or may not come with ephemeral resource disks
depending on the VM SKU. For VM SKUs that come with
ephemeral resource disks, the Azure platform guarantees that
the ephemeral resource disk is attached to the VM before
the VM is booted. For VM SKUs that do not come with
ephemeral resource disks, cloud-init currently attempts
to wait and set up a non-existent ephemeral resource
disk, which wastes boot time. It also causes disk setup
modules to fail (due to non-existent references to the
ephemeral resource disk).
udevadm settle is invoked by cloud-init very early in boot.
udevadm settle is invoked very early, before
DataSourceAzure's _get_data() and activate() methods.
Within DataSourceAzure's _get_data() and activate() methods,
the ephemeral resource disk path should exist if the
VM SKU comes with an ephemeral resource disk.
The ephemeral resource disk path should not exist if the
VM SKU does not come with an ephemeral resource disk.
LP: #1901011
Diffstat (limited to 'tests/integration_tests/bugs/test_lp1886531.py')
0 files changed, 0 insertions, 0 deletions