yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

This is believed fixed in 17.1

** Changed in: cloud-init
       Status: Fix Committed => Fix Released

-- 
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/1660385

Title:
  Alert user of Ec2 Datasource on lookalike cloud

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Opportunistic polling of the Ec2 Metadata service, which lives at
  169.254.169.254 can be problematic for numerous reasons including timeouts.

  In this first phase of SRU, the code that has been added will be set to
  a warn-only mode.

  In 16.04, if cloud-init finds it is using a EC2 Metadata Service but
  not running on Amazon AWS, it will warn the user.

  In 16.10, it will warn the user and sleep 10 seconds to increase the
  likelyhood of being noticed.

  [Test Case]

  a.) check warnings are seen on openstack configured to use ec2
   - launch instance on openstack (it will use OpenStack MD)
   - enable proposed upgrade
   - rm -Rf /var/lib/cloud /var/log/cloud-init*
   - dpkg-reconfigure cloud-init
     # select 'Ec2' and 'None' only
   - sudo reboot
   - ssh in. you should see a warning.
     The warning instructs you to silence the warning by putting
     the following in /etc/cloud/cloud.cfg.d/99-ec2-datasource.cfg. Do that.
      | datasource:
      |  Ec2:
      |   strict_id: false
   - rm -Rf /var/lib/cloud/ /var/log/cloud*
   - reboot
   - ssh in. you should not see a warning.

  
  [Regression Potential]
  There is real regression potential here.  That is why we have announced
  this fairly widely and also are putting this into place with warnings
  only first.

  After some time is passed, further SRUs will put more strict behavior
  in place.

  [Other Info]
  We've announced this fairly widely on mailing lists
   https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039697.html
  === End SRU Template ===

  Many cloud providers mimic the EC2 Metadata service [1] in order to
  provide a level of EC2 compatibility for images.  This is quite useful and
  allows image portability.

  Because this is a network based metadata service, cloud-init
  opportunistically poll an IPv4 link local address (http://169.254.169.254)
  to determine if there is metadata available.  That can have negative side
  affects such as timeouts.

  AWS has recently begun providing a way for instances to determine if they
  are running on EC2 [2].

  Cloud-init will change its behavior to attempt to find the EC2 metadata
  service only if it has determined itself to be running on EC2 or another
  known cloud provider which provides an EC2 metadata service.

  For more information, please see:
    https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039697.html

  --
  [1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html
  [2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/identify_ec2_instances.html

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