ds-identify needs to support check_instance_id like function

Bug #1680116 reported by Scott Moser on 2017-04-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

When ds-identify runs, it identifies the cloud platform based on available information.
For some datasources provided as an attached disk, the cloud provider may remove that disk at some time (or potentially, the user might destroy it). In such cases (Azure and ConfigDrive) the system id read from smbios is the same as the instance-id, so we can locally quickly check.

cloud-init's datasource search code supports this via the 'check_instance_id' method in a datasource.
Basically, that function is called from the old datasource. If it retunrs true, then cloud-init would not go looking for an attached disk that it would not find.

The ds-identify code does not support this at the moment. The result is if you did:
 * boot system with configdrive
 * dd if=/dev/zero of=/dev/disk/by-name/config-2
 * reboot

ds-identify would then not recognize this system as config drive even though the datasource would recognize it was.

Scott Moser (smoser) on 2017-04-05
Changed in cloud-init:
status: New → Triaged
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers