yahoo-eng-team team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New

Thank you.

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

Title:
  ec2: xenial unnecessary  openstack datasource probes during discovery

Status in cloud-init:
  Fix Released

Bug description:
  Now that OpenStack datasource is detected at init-local timeframe,
  that discovery can occur before Ec2 datasource. As a result, cloud-
  init integration tests started failing becuase of unexpected WARNINGs
  in cloud-init.log [1].

  The unexpected warning message is emitted by OpenStack.get_data
  probing for openstack metadata service when it should instead check
  whether the environment is ec2 and exit False to avoid wasting cycles.

  Unexpected warning: ['2018-06-10 01:11:08,101 - util.py[WARNING]: No
  active metadata service found']

  References:
  [1] failed jenkins integration test: https://jenkins.ubuntu.com/server/view/cloud-init,%20curtin,%20streams/job/cloud-init-integration-ec2-x/23/console

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