cloud-init

The meaning of "Changes to it will not persist across an instance." in 50-cloud-init.yaml is unclear

Bug #1845669 reported by Dan Watkins on 2019-09-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
​ cloud-init
Fix Released
Undecided
Dan Watkins
Also affects project (?) Also affects distribution/package Nominate for series

Bug Description

What does "across an instance" mean?

Related branches

~oddbloke/cloud-init/+git/cloud-init:net
Chad Smith: Approve on 2019-09-27
Server Team CI bot: Approve (continuous-integration) on 2019-09-27
Diff: 89 lines (+17/-16)
3 files modified
cloudinit/distros/debian.py (+6/-5)
cloudinit/distros/ubuntu.py (+2/-2)
tests/unittests/test_distros/test_netconfig.py (+9/-9)
Dan Watkins (oddbloke) on 2019-09-27
Changed in cloud-init:
assignee: nobody → Dan Watkins (daniel-thewatkins)
Server Team CI bot (server-team-bot) wrote :

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

Changed in cloud-init:
status: New → Fix Committed
Chad Smith (chad.smith) wrote : Fixed in cloud-init version 19.2-52.

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

Other bug subscribers