diff options
| author | Chad Smith <chad.smith@canonical.com> | 2021-02-19 15:37:57 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-02-19 15:37:57 -0700 |
| commit | 66e2d42dd1b722dc8e59f4e5990cea54f81ccd2a (patch) | |
| tree | da3d84ce220872f47c42210bb59a2fce58883cb8 /tox.ini | |
| parent | 08d8902a95407d1f313ba1c679145d5f6b0df455 (diff) | |
| download | vyos-cloud-init-66e2d42dd1b722dc8e59f4e5990cea54f81ccd2a.tar.gz vyos-cloud-init-66e2d42dd1b722dc8e59f4e5990cea54f81ccd2a.zip | |
azure: case-insensitive UUID to avoid new IID during kernel upgrade (#798)
Kernel's newer than 4.15 present /sys/dmi/id/product_uuid as a
lowercase value. Previously UUID was uppercase.
Azure datasource reads the product_uuid directly as their platform's
instance-id. This presents a problem if a kernel is either
upgraded or downgraded across the 4.15 kernel version boundary because
the case of the UUID will change, resulting in cloud-init seeing a
"new" instance id and re-running all modules.
Re-running cc_ssh in cloud-init deletes and regenerates ssh_host keys
on a system which can cause concern on long-running instances that
somethingnefarious has happened.
Also add:
- An integration test for this for Azure Bionic Ubuntu FIPS upgrading from
a FIPS kernel with uppercase UUID to a lowercase UUID in linux-azure
- A new pytest.mark.sru_next to collect all integration tests related to our
next SRU
LP: #1835584
Diffstat (limited to 'tox.ini')
| -rw-r--r-- | tox.ini | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -184,5 +184,6 @@ markers = instance_name: the name to be used for the test instance sru_2020_11: test is part of the 2020/11 SRU verification sru_2021_01: test is part of the 2021/01 SRU verification + sru_next: test is part of the next SRU verification ubuntu: this test should run on Ubuntu unstable: skip this test because it is flakey |