yahoo-eng-team team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

Hi,

I *do* want to fix cloud-init to accept your specific configuration
of openstack datasource.  The plan is to fix that under bug 1788487.

I think you're suggesting that you are running nova-lxd as your
platform.  Is that correct?

We have a couple options then to fix this:
a.) cloud-init fix bug 1788487, allowing you to manually put
'datasource_list: [OpenStack]' into the image somewhere in
/etc/cloud/cloud.cfg.d/

b.) Get openstack team to release a Stable Release Update(SUR) to 16.04
for bug 1661797.
It looks like a previous nova-lxd SRU upload has stalled for bug 1675386.
Hopefully we can get that let in and then we could investigate doing the
SRU for platform identification here.

c.) you could cherry-pick the fix for bug 1661791 into your nova-lxd
The one line change at 
https://review.openstack.org/#/c/431247/1 might be easier to cherry-pick
and should suffice.

'c' is the quickest fix for you.
'b' or 'c' allows you to run bionic guests as well.



** Changed in: cloud-init
   Importance: Undecided => Medium

** Changed in: cloud-init
       Status: New => Confirmed

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu)
       Status: New => Confirmed

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

-- 
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:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed

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