ec2: xenial unnecessary openstack datasource probes during discovery

[ubuntu-server-builder]

This bug was originally filed in Launchpad as LP: #1776701

Launchpad details

affected_projects = []
assignee = chad.smith
assignee_name = Chad Smith
date_closed = 2018-06-20T18:05:32.977402+00:00
date_created = 2018-06-13T16:03:23.236833+00:00
date_fix_committed = 2018-06-16T01:37:02.952993+00:00
date_fix_released = 2018-06-20T18:05:32.977402+00:00
id = 1776701
importance = high
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1776701
milestone = None
owner = chad.smith
owner_name = Chad Smith
private = False
status = fix_released
submitter = chad.smith
submitter_name = Chad Smith
tags = []
duplicates = []

Launchpad user Chad Smith(chad.smith) wrote on 2018-06-13T16:03:23.236833+00:00

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

[ubuntu-server-builder]

Launchpad user Chad Smith(chad.smith) wrote on 2018-06-16T01:37:01.611245+00:00

An upstream commit landed for this bug.

To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=1efa8a0a

[ubuntu-server-builder]

Launchpad user Scott Moser(smoser) wrote on 2018-06-20T18:05:33.814012+00:00

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.