yahoo-eng-team team mailing list archive

[Chad Smith <1756471@xxxxxxxxxxxxxxxxxx>]

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1756471

Title:
  ds-identify does not identify openstack  Open Telecom Cloud

Status in cloud-init:
  Fix Released

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 ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1756471/+subscriptions