EC2 datasource moved to init-local stage

Bug #1709772 reported by Chad Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Fix Released
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)
Changed in cloud-init:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Chad Smith (chad.smith)
Chad Smith (chad.smith)
Changed in cloud-init:
status: In Progress → Fix Committed
Revision history for this message
Scott Moser (smoser) wrote : Fixed in Cloud-init 17.1

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
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.