ds-identify does not identify openstack Open Telecom Cloud
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Unassigned |
Bug Description
from a comment in bug 1669675.
The OpenStack detection fails on the 1st gen compute hosts (using Xen hypervisor) in the Open Telekom Cloud.
Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Xen
Product Name: HVM domU
Version: 4.1.2_115-908.762.
Serial Number: 3c569b61-
UUID: 3C569B61-
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified
Handle 0x0300, DMI type 3, 13 bytes
Chassis Information
Manufacturer: Xen
Type: Other
Lock: Not Present
Version: Not Specified
Serial Number: Not Specified
Asset Tag: OpenTelekomCloud
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: Unknown
Detection in ds-identify could look for Xen (HVM domU) and the Asset Tag.
... Alternatively, the UUID looks also suspiciously like OpenStack ...
Related branches
- Chad Smith: Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 51 lines (+15/-0)2 files modifiedtests/unittests/test_ds_identify.py (+11/-0)
tools/ds-identify (+4/-0)
- cloud-init Commiters: Pending requested
-
Diff: 39 lines (+11/-5)1 file modifiedtools/ds-identify (+11/-5)
Changed in cloud-init: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in cloud-init: | |
status: | Triaged → Fix Committed |
Kurt,
Could you please run:
cloud-init collect-logs
and attach the output here?
And also:
$ sudo sh -c 'cd /sys/hypervisor && grep -r . *'
$ sudo sh -c 'cd /sys/class/dmi/id && grep -r . *'
Thank you.