ds-identify does not identify openstack Open Telecom Cloud

Bug #1756471 reported by Scott Moser on 2018-03-17
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
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-463d-49e0-ad09-c5e2235ce658
 UUID: 3C569B61-463D-49E0-AD09-C5E2235CE658
 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

Scott Moser (smoser) wrote :

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.

Kurt Garloff (kgarloff) wrote :

Hi Scott,
we have patched cloud-init to work on OTC ...

--- cloud-init/ds-identify.orig 2018-03-16 21:29:14.947288849 +0100
+++ cloud-init/ds-identify 2018-03-16 21:33:08.168871245 +0100
@@ -832,7 +832,10 @@ dscheck_OpenStack() {
     if [ "${DI_PID_1_PRODUCT_NAME}" = "$nova" ]; then
         return ${DS_FOUND}
     fi
-
+ if dmi_chassis_asset_tag_matches "OpenTelekomCloud"; then
+ return ${DS_FOUND}
+ fi
+
     # LP: #1715241 : arch other than intel are not identified properly.
     case "$DI_UNAME_MACHINE" in
         i?86|x86_64) :;;

I assume you want me to collect logs from an unpatched VM?

Contents of /sys/hypervisor and /sys/class/dmi/id from VMs on 1st gen XEN hosts on OTC attached.

Kurt Garloff (kgarloff) wrote :
Scott Moser (smoser) on 2018-03-19
Changed in cloud-init:
status: New → Triaged
importance: Undecided → Medium
Chad Smith (chad.smith) on 2018-03-22
Changed in cloud-init:
status: Triaged → Fix Committed
Chad Smith (chad.smith) wrote :

An upstream commit landed for this bug.

To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=77137132

This bug is believed to be fixed in cloud-init in 18.2. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers