read_dmi_data warning confusing when key not found and no dmidecode
Bug #1702721 reported by
Ryan Harper
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-init |
Expired
|
Low
|
Unassigned | ||
Bug Description
On systems without dmidecode and where the dmi key is not present, cloud-init will print this warning:
LOG.warning("did not find either path %s or dmidecode command",
Which looks strange since the system does have /sys/class/dmi/id but just did not find the requested key.
This is due to _read_dmi_syspath returning None and which('dmidecode') returning None.
Ideally we'd indicate that we couldn't read the specified key separately from the case where the system doesn't have /sys/class/dmi/id.
Revision history for this message
| Ryan Harper (raharper) wrote | #1 |
| Changed in cloud-init: | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
Revision history for this message
| James Falcon (falcojr) wrote | #2 |
| Changed in cloud-init: | |
| status: | Confirmed → Expired |
To post a comment you must log in.
This issue can be observed when running under Ubuntu-Core (which has no dmidecode tool)