yahoo-eng-team team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

** Changed in: cloud-init
       Status: Incomplete => Invalid

** Changed in: cloud-init (Ubuntu)
       Status: Incomplete => Invalid

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

Title:
  cloud-init fails openstack detection from openstack lxd virtual
  instances

Status in cloud-init:
  Invalid
Status in cloud-init package in Ubuntu:
  Invalid

Bug description:
  Hi,
   I'm using openstack (2:13.1.3-0ubuntu1) in a on-premise cloud to
  manage, among other types, LXD ubuntu bionic virtual instances
  (that run cloud-init version 18.3-9-g2e62cb8a-0ubuntu1~18.04.2),
  and unfortunately the DataSourceOpenStack.py module fails to detect
  openstack's presence, even if explicitely configured as the only data
  source with "datasource_list: [ OpenStack ]".

  After some investigation, I found that the detect_openstack function
  fails because:

  1) read_dmi_data always returns None because it detects to be inside a
     container ("systemd-detect-virt --container" returns "lxc")

  2) even if 1) worked, none of the openstack detection rules would match: 
      "/proc/1/environ" does not contain "product_name=OpenStack Nova"
     (it contains "container=lxc" instead), DMI
      product_name is not "Openstack Nova" nor "OpenStack Compute" and
      DMI chassis_asset_tag is not "OpenTelekomCloud".

  The same configuration worked well with the previous version of
  cloud-init that did not enforce openstack detection.

  Any advice for a proper solution? Is there any configuration to force
  Openstack detection?

  Note that... replacing "detect_openstack"'s content with "return
  True", everything works correctly.

  Thank you!

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