yahoo-eng-team team mailing list archive

[Adrian Vladu <1895976@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Because of the commit that introduced platform checks for enabling /
using http openstack metadata (https://github.com/canonical/cloud-
init/commit/1efa8a0a030794cec68197100f31a856d0d264ab), Linux machines
will stop loading http metadata when running on "unsupported" platforms
/ hypervisors like Hyper-V, XEN, OracleCloud, VMware, OpenTelekomCloud -
leading to a whole suite of bug reports and fixes to a non-issue.

Let's try to solve this problem once for all the upcoming platforms /
hypervisors by adding a configuration option on the metadata level:
platform_check or is_platform_supported (suggestions are welcome for the
naming). The value of the config option should be true in order to
maintain backwards compatibility.

No one would like to patch well-working OpenStack environments for this
kind of issues and it is always easier to control / build the images you
use on private OpenStack.

** Affects: cloud-init
     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/1895976

Title:
  Fail to get http openstack metadata if the Linux instance runs on
  Hyper-V

Status in cloud-init:
  New

Bug description:
  Because of the commit that introduced platform checks for enabling /
  using http openstack metadata (https://github.com/canonical/cloud-
  init/commit/1efa8a0a030794cec68197100f31a856d0d264ab), Linux machines
  will stop loading http metadata when running on "unsupported"
  platforms / hypervisors like Hyper-V, XEN, OracleCloud, VMware,
  OpenTelekomCloud - leading to a whole suite of bug reports and fixes
  to a non-issue.

  Let's try to solve this problem once for all the upcoming platforms /
  hypervisors by adding a configuration option on the metadata level:
  platform_check or is_platform_supported (suggestions are welcome for
  the naming). The value of the config option should be true in order to
  maintain backwards compatibility.

  No one would like to patch well-working OpenStack environments for
  this kind of issues and it is always easier to control / build the
  images you use on private OpenStack.

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