cloud-init on xenial may generate network config on every boot
Bug #1819913 reported by
Ryan Harper
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
- Server Team CI bot: Approve (continuous-integration)
- Ryan Harper: Approve
-
Diff: 89 lines (+27/-4)4 files modifiedcloudinit/sources/DataSourceScaleway.py (+2/-1)
cloudinit/sources/__init__.py (+3/-3)
cloudinit/sources/tests/test_init.py (+15/-0)
tests/unittests/test_datasource/test_scaleway.py (+7/-0)
Revision history for this message
| Ryan Harper (raharper) wrote | #1 |
| 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 | #2 |
| Changed in cloud-init: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Chad Smith (chad.smith) wrote Fixed in cloud-init version 19.1. | #3 |
| Changed in cloud-init: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Chad Smith (chad.smith) wrote | #4 |
| Changed in cloud-init: | |
| status: | Fix Released → New |
| Changed in cloud-init: | |
| status: | New → Confirmed |
Revision history for this message
| Chad Smith (chad.smith) wrote Fixed in cloud-init version 19.3. | #5 |
| Changed in cloud-init: | |
| status: | Confirmed → Fix Released |
Revision history for this message
| James Falcon (falcojr) wrote | #6 |
To post a comment you must log in.
cloud-init collect-logs from ec2 instance.