NoCloud SMBIOS seed broken in 23.4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
High
|
James Falcon | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Mantic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[ Impact ]
In cloud-init 23.4, specifying a datasource via the SMBIOS is broken. This is due to a commit that fixed another bug of cloud-init assuming a datasource list consisting of one datasource and 'None' doesn't need to check for the existence of that datasource. The fix here is to ensure we're always checking for the SMBIOS information, whereas in the past we didn't need to because of the automatic datasource assumption.
[ Test Plan ]
An integration test has been added upstream as part of https:/
tox -e integration-tests -- tests/integrati
[ Where problems could occur ]
Since this code sits at the interaction of datasources discovered and found via ds-identify and python, along with bits of fallback code to dmidecode, we could have missed an interaction here that could possibly mis-identify the NoCloud datasource in other ways.
[ Other Info ]
Upstream bug: https:/
Upstream dup: https:/
Documentation of specifying NoCloud datasource via SMBIOS :
https:/
Upstream PR with change that broke the cloud-init behavior:
https:/
Upstream PR fixing the behavior:
https:/
description: | updated |
tags: | added: regression-update |
description: | updated |
description: | updated |
Changed in cloud-init (Ubuntu): | |
status: | New → In Progress |
description: | updated |
Upstream PR landed fixing this issue: /github. com/canonical/ cloud-init/ commit/ 66b5ce9d5f94c0c 6625972fdfdca37 96d365b069
https:/
upstream commit with integration test for ongoing validaiton of this behavior: /github. com/canonical/ cloud-init/ commit/ 4b694a45db2f904 3700e6a619bb943 086be2f0c9
https:/