yahoo-eng-team team mailing list archive

[James Falcon <1683038@xxxxxxxxxxxxxxxxxx>]

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

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

** 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/1683038

Title:
  Need to convince cloud-init we really want Ec2 datasource

Status in cloud-init:
  Expired
Status in diskimage-builder:
  Fix Released

Bug description:
  cloud-init was recently changed to be more selective about the types
  of data source it wants to access.  See
  https://bugs.launchpad.net/cloud-init/+bug/1660385.  In particular,
  when it is run on a non-EC2 cloud and sees EC2 metadata, it recently
  started to print annoying warnings to the user.

  When we add the "Ec2" datasource to images, we should also generate a
  workaround that suppresses the warning.  According to the warning
  itself, this can be achieved by adding a file
  /etc/cloud/cloud.cfg.d/99-ec2-datasource.cfg that says

    #cloud-config
    datasource:
     Ec2:
      strict_id: false

  An alternative would be to live with the warnings, and hope that DIB
  users select other datasources in preference of Ec2, for example
  OpenStack and/or ConfigDrive.

  Another option would be to convince the cloud-init developers that
  OpenStack clouds can be expected to provide the Ec2 metadata service,
  and that there's no need to issue warnings about that.

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