This bug is believed to be fixed in cloud-init in 18.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
--
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/1747070
Title:
ds-identify does not see nocloud seed in core snap
Status in cloud-init:
Fix Released
Bug description:
If ubuntu-image is built with cloud-config, it puts data into
/writable/system-data/var/lib/cloud.
That directory is then bind mounted to /var/lib/cloud via /etc/fstab etnry
like:
/writable/system-data/var/lib/cloud /var/lib/cloud none bind 0 0
ds-identify, which is run from
/lib/systemd/system-generators/cloud-init-generator runs before /var/lib/cloud
bind mount is done, so it does not see the seed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1747070/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
