yahoo-eng-team team mailing list archive

[Mark <1788487@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: cloud-init
     Importance: Undecided
         Status: New

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

** Description changed:

  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. #1784685) and is also broken for VMware.
+ several cloud platforms (e.g. LP: #1784685) and is also broken for
+ VMware.
  
- As can be seen in #1669875 there is no way to discern OpenStack on
+ 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.

** Description changed:

  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.
+ original goal in LP: 1efa8a0a030794cec68197100f31a856d0d264ab.

** Description changed:

  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 LP: 1efa8a0a030794cec68197100f31a856d0d264ab.
+ 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.

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

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

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