This bug was fixed in the package nova-lxd - 14.2.2-0ubuntu0.16.10.2
---------------
nova-lxd (14.2.2-0ubuntu0.16.10.2) yakkety; urgency=medium
* d/p/bug1691428-ocata.patch: Cherry pick fix to ensure that readonly
flag for config-drive device is correctly passed to LXD
(LP: #1691428).
nova-lxd (14.2.2-0ubuntu0.16.10.1) yakkety; urgency=medium
* New upstream point release for Openstack Newton (LP: #1673411)
-- James Page <james.p...@ubuntu.com> Wed, 17 May 2017 11:12:17 +0100
** Changed in: nova-lxd (Ubuntu Yakkety)
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/1673411
Title:
config-drive support is broken
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive newton series:
Fix Committed
Status in Ubuntu Cloud Archive ocata series:
Fix Released
Status in cloud-init:
Fix Committed
Status in nova-lxd:
Fix Released
Status in nova-lxd newton series:
Fix Released
Status in nova-lxd ocata series:
Fix Released
Status in nova-lxd trunk series:
Fix Released
Status in cloud-init package in Ubuntu:
Fix Released
Status in nova-lxd package in Ubuntu:
Fix Released
Status in cloud-init source package in Xenial:
Fix Released
Status in nova-lxd source package in Xenial:
Invalid
Status in cloud-init source package in Yakkety:
Fix Released
Status in nova-lxd source package in Yakkety:
Fix Released
Status in cloud-init source package in Zesty:
Fix Released
Status in nova-lxd source package in Zesty:
Fix Released
Bug description:
=== Begin cloud-init SRU Template ===
[Impact]
nova-lxd can provide data to instances in 2 ways:
a.) metadata service
b.) config drive
The support for reading the config drive in cloud-init was never
functional. Nova-lxd has changed the way they're presenting the config
drive to the guest. Now they are doing so by populating a directory in
the container /config-drive with the information.
The change added to cloud-init was to extend support read config drive
information from that directory.
[Test Case]
With a nova-lxd that contains the fix this can be fully tested
by launching an instance with updated cloud-init and config drive
attached.
For cloud-init, the easiest way to demonstrate this is to
create a lxc container and populate it with a '/config-drive'.
lxc-proposed-snapshot is
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot
It publishes an image to lxd with proposed enabled and cloud-init upgraded.
$ release=xenial
$ ref=xenial-proposed
$ name=$release-lp1673411
$ lxc-proposed-snapshot --proposed --publish $release $ref
$ lxc init $ref $name
# lxc will create the 'NoCloud' seed, and the normal search
# path looks there first, so remove it.
$ lxc file pull $name/etc/cloud/cloud.cfg.d/90_dpkg.cfg - |
sed 's/NoCloud, //' |
lxc file push - $name/etc/cloud/cloud.cfg.d/90_dpkg.cfg
## populate a /config-drive with attached 'make-config-drive-dir'
## and push it to the container
$ d=$(mktemp -d)
$ make-config-drive-dir "$d" "$name"
$ rm -Rf "$d"
## start it and look around
$ lxc start $name
$ sleep 10
$ lxc exec $name cat /run/cloud-init/result.json
{
"v1": {
"datasource": "DataSourceConfigDrive [net,ver=2][source=/config-drive]",
"errors": []
}
}
[Regression Potential]
There is a potentiali false positive where a user had data in
/config-drive and now that information is read as config drive data.
That would require a directory tree like:
/config-drive/openstack/2???-??-??/meta_data.json
or
/config-drive/openstack/latest/meta_data.json
Which seems like a small likelyhood of non-contrived hit.
[Other Info]
Upstream commit:
https://git.launchpad.net/cloud-init/commit/?id=443095f4d4b6fe
=== End cloud-init SRU Template ===
After reviewing https://review.openstack.org/#/c/445579/ and doing
some testing, it would appear that the config-drive support in the
nova-lxd driver is not functional.
cloud-init ignores the data presented in /var/lib/cloud/data and reads
from the network accessible metadata-service.
To test this effectively you have to have a fully offline instance
(i.e. no metadata service access).
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1673411/+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
