cloud-init

cloud-init on xenial may generate network config on every boot

Bug #1819913 reported by Ryan Harper on 2019-03-13

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	cloud-init	Fix Released	Undecided	Dan Watkins

Bug Description

On at least EC2 with cloud-init xenial release, the Ec2 datasource allows the EventType.BOOT
event to update metadata and will regenerate network configuration on each boot. Cloud-init releases newer than Xenial are not affected since cloud-init will detect
which datasource to use and does not perform searching.

Related branches

~oddbloke/cloud-init/+git/cloud-init:ds_update_events

Merged into cloud-init:master

Server Team CI bot: Approve (continuous-integration) on 2019-03-14

Ryan Harper: Approve on 2019-03-14

Revision history for this message

Ryan Harper (raharper) wrote on 2019-03-13:

cloud-init.tar.gz Edit (67.5 KiB, application/x-tar)

cloud-init collect-logs from ec2 instance.

Dan Watkins (oddbloke) on 2019-03-14

Changed in cloud-init:
status:	New → In Progress
assignee:	nobody → Dan Watkins (daniel-thewatkins)

Revision history for this message

Server Team CI bot (server-team-bot) wrote on 2019-03-14:

This bug is fixed with commit f2fd6eac to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=f2fd6eac

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

Revision history for this message

Chad Smith (chad.smith) wrote on 2019-05-10: Fixed in cloud-init version 19.1.

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

Chad Smith (chad.smith) wrote on 2019-05-17:

The content fixing this was subsequently reverted due to causing tracebacks on upgrade path
https://git.launchpad.net/cloud-init/commit/?id=6322c2ddf4b68a8e7cc467a07fb20a1d151a2ef3

reopening until a resolution is provided

Changed in cloud-init:
status:	Fix Released → New

Chad Smith (chad.smith) on 2019-05-17

Changed in cloud-init:
status:	New → Confirmed

Revision history for this message

Chad Smith (chad.smith) wrote on 2019-11-05: Fixed in cloud-init version 19.3.

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

Thank you.