EC2 datasource moved to init-local stage

Bug #1709772 reported by Chad Smith on 2017-08-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Medium
Chad Smith

Bug Description

In EC2 clouds, the only way to determine whether an instance is configured for IPv6 is by querying the metadata service. In order to query metadata to determine network configuration, DataSourceEc2 needs to configure the network with dhcp and then query the datasource.

Add optional functionality for DataSourceEc2 to query metatadata sevice in init-local timeframe using dhcp.

Related branches

Chad Smith (chad.smith) on 2017-08-10
Changed in cloud-init:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Chad Smith (chad.smith)
Chad Smith (chad.smith) on 2017-08-10
Changed in cloud-init:
status: In Progress → Fix Committed

This bug is believed to be fixed in cloud-init in 17.1. 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