ec2: xenial unnecessary openstack datasource probes during discovery

Bug #1776701 reported by Chad Smith on 2018-06-13
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloud-init
High
Chad Smith

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

Related branches

Chad Smith (chad.smith) on 2018-06-13
Changed in cloud-init:
importance: Undecided → High
assignee: nobody → Chad Smith (chad.smith)
status: New → In Progress
Chad Smith (chad.smith) wrote :

An upstream commit landed for this bug.

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

Changed in cloud-init:
status: In Progress → Fix Committed

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers