This bug is believed to be fixed in cloud-init in version 18.4. 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
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1791781
Title:
instance-data.json not persisted across reboot.
Status in cloud-init:
Fix Released
Bug description:
cloud-init v18.3 /run/cloud-init/instance-data.json does not persist
across reboot.
Affects: Xenial series or later
Any attempt by services/consumers to re-use instance data after a machine
reboots will fail.
To reproduce:
$ lxc launch ubuntu-daily:xenial test-xenial
Creating test-xenial
Starting test-xenial
$ lxc exec test-xenial cat
/ruc/cloud-init/instance-data.json/cloud-init/instance-data.json
{
"base64-encoded-keys": [
"ds/vendor-data",
...
$ lxc exec test-xenial reboot
$ lxc exec test-xenial cat /ruc/cloud-init/instance-data.json
cat: /run/cloud-init/instance-data.json: No such file or directory
Note: cloud-init only writes instnace-data.json when processing meta-
data on the 1st boot via DataSource.get_data call. We either need to
persist this data somewhere else, or write it again per boot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1791781/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
