yahoo-eng-team team mailing list archive

[James Falcon <1788487@xxxxxxxxxxxxxxxxxx>]

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

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

** Changed in: cloud-init
       Status: Confirmed => 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/1788487

Title:
  OpenStack detection broken on VMware

Status in cloud-init:
  Expired
Status in cloud-init package in Ubuntu:
  Confirmed

Bug description:
  The OpenStack data source in cloud-init 18.3 was updated to detect
  OpenStack systems before probing the metadata endpoint. This broke for
  several cloud platforms (e.g. LP: #1784685) and is also broken for
  VMware.

  As can be seen in LP: #1669875 there is no way to discern OpenStack on VMware from DMI data. A way around this could be to generally add 'VMware Virtual Platform' to the list of valid DMI platform names (`VALID_DMI_PRODUCT_NAMES`). This should still avoid the OpenStack metadata probe on most (if not all) other cloud platforms, as was the original goal in
  https://git.launchpad.net/cloud-init/commit/?id=1efa8a0a030794cec68197100f31a856d0d264ab.

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