yahoo-eng-team team mailing list archive

[James Falcon <1828236@xxxxxxxxxxxxxxxxxx>]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3378

** Bug watch added: github.com/canonical/cloud-init/issues #3378
   https://github.com/canonical/cloud-init/issues/3378

** Changed in: cloud-init
       Status: Triaged => Expired

-- 
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/1828236

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

Status in cloud-init:
  Expired

Bug description:
  relating to cloud-init bugs #1669675 #1756471

  
  The OpenStack detection fails on BMS (Bare Metal) hosts in Open Telekom Cloud.

  cloud-init version 18.5 detection fails
  cloud-init Version 18.2 still works 

  /usr/lib/python3/dist-packages/cloudinit/sources/DataSourceOpenStack.py searches for
  (...) 
  # OpenStack DMI constants
  DMI_PRODUCT_NOVA = 'OpenStack Nova'
  DMI_PRODUCT_COMPUTE = 'OpenStack Compute'
  VALID_DMI_PRODUCT_NAMES = [DMI_PRODUCT_NOVA, DMI_PRODUCT_COMPUTE]
  DMI_ASSET_TAG_OPENTELEKOM = 'OpenTelekomCloud'
  VALID_DMI_ASSET_TAGS = [DMI_ASSET_TAG_OPENTELEKOM]
  (...)
   
  BMS server in OTC have none of theses tags set.
  Manual edit DataSourceOpenStack.py only for testing to accept our host, all is working fine.

  How we can get back OTC BMS hosts detected as valid OpenStack hosts in
  cloud-init?

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