Activity log for bug #1673411

Date Who What changed Old value New value Message
2017-03-16 10:37:54 James Page bug added bug
2017-03-16 10:39:03 James Page nova-lxd: importance Undecided Medium
2017-03-16 12:01:26 James Page nova-lxd: status New Confirmed
2017-03-16 12:01:55 James Page nova-lxd: status Confirmed Triaged
2017-03-16 14:35:16 James Page bug task added cloud-init
2017-03-16 15:22:14 Launchpad Janitor merge proposal linked https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/320069
2017-03-16 15:24:36 Scott Moser cloud-init: status New Confirmed
2017-03-16 15:24:38 Scott Moser cloud-init: importance Undecided Medium
2017-03-16 15:25:04 Scott Moser attachment added deb built from tip of merge branch https://bugs.launchpad.net/cloud-init/+bug/1673411/+attachment/4838993/+files/cloud-init_0.7.9-61-gcbf0344-1~bddeb_all.deb
2017-03-16 15:46:35 Scott Moser bug added subscriber Scott Moser
2017-03-16 15:46:51 Scott Moser attachment removed deb built from tip of merge branch https://bugs.launchpad.net/cloud-init/+bug/1673411/+attachment/4838993/+files/cloud-init_0.7.9-61-gcbf0344-1~bddeb_all.deb
2017-03-16 15:48:32 Scott Moser attachment added updated deb https://bugs.launchpad.net/cloud-init/+bug/1673411/+attachment/4838995/+files/cloud-init_0.7.9-61-g3fab1ec-1~bddeb_all.deb
2017-03-16 15:48:57 Lubosz Kosnik bug added subscriber Lubosz Kosnik
2017-03-16 16:46:58 Scott Moser attachment removed updated deb https://bugs.launchpad.net/nova-lxd/+bug/1673411/+attachment/4838995/+files/cloud-init_0.7.9-61-g3fab1ec-1~bddeb_all.deb
2017-03-16 16:56:16 Scott Moser attachment added cloud-init_0.7.9-61-g4508604-1~bddeb_all.deb https://bugs.launchpad.net/nova-lxd/+bug/1673411/+attachment/4839010/+files/cloud-init_0.7.9-61-g4508604-1~bddeb_all.deb
2017-03-20 14:45:34 David Coronel bug added subscriber David Coronel
2017-03-20 16:13:33 Dominique Poulain bug added subscriber Dominique Poulain
2017-03-24 08:25:03 OpenStack Infra nova-lxd: status Triaged Fix Released
2017-03-24 09:32:47 James Page nominated for series nova-lxd/ocata
2017-03-24 09:32:47 James Page bug task added nova-lxd/ocata
2017-03-24 09:32:47 James Page nominated for series nova-lxd/mitaka
2017-03-24 09:32:47 James Page bug task added nova-lxd/mitaka
2017-03-24 09:32:47 James Page nominated for series nova-lxd/trunk
2017-03-24 09:32:47 James Page bug task added nova-lxd/trunk
2017-03-24 09:32:47 James Page nominated for series nova-lxd/newton
2017-03-24 09:32:47 James Page bug task added nova-lxd/newton
2017-03-24 09:33:02 James Page bug task added nova-lxd (Ubuntu)
2017-03-24 09:33:13 James Page nominated for series Ubuntu Zesty
2017-03-24 09:33:13 James Page bug task added nova-lxd (Ubuntu Zesty)
2017-03-24 09:33:13 James Page nominated for series Ubuntu Yakkety
2017-03-24 09:33:13 James Page bug task added nova-lxd (Ubuntu Yakkety)
2017-03-24 09:33:13 James Page nominated for series Ubuntu Xenial
2017-03-24 09:33:13 James Page bug task added nova-lxd (Ubuntu Xenial)
2017-03-24 09:33:26 James Page nova-lxd (Ubuntu Xenial): importance Undecided High
2017-03-24 09:33:26 James Page nova-lxd (Ubuntu Xenial): status New Triaged
2017-03-24 09:34:12 James Page bug task deleted nova-lxd (Ubuntu Xenial)
2017-03-24 09:34:20 James Page bug task deleted nova-lxd/mitaka
2017-03-24 09:34:56 James Page nova-lxd/ocata: importance Undecided Medium
2017-03-24 09:35:01 James Page nova-lxd/newton: importance Undecided Medium
2017-03-24 09:35:04 James Page nova-lxd (Ubuntu Yakkety): importance Undecided Medium
2017-03-24 09:35:07 James Page nova-lxd (Ubuntu Zesty): importance Undecided Medium
2017-03-24 09:35:15 James Page nova-lxd (Ubuntu Yakkety): status New Triaged
2017-03-24 09:35:19 James Page nova-lxd (Ubuntu Zesty): status New Triaged
2017-03-24 09:35:26 James Page nova-lxd/ocata: status New Triaged
2017-03-24 09:35:29 James Page nova-lxd/newton: status New Triaged
2017-03-24 09:51:41 OpenStack Infra nova-lxd/ocata: status Triaged Fix Committed
2017-03-24 09:57:23 OpenStack Infra nova-lxd/newton: status Triaged Fix Committed
2017-03-24 20:48:08 Launchpad Janitor merge proposal linked https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/320986
2017-03-27 17:38:48 Scott Moser bug task added cloud-init (Ubuntu)
2017-03-27 17:39:09 Scott Moser cloud-init: status Confirmed Fix Committed
2017-03-27 17:39:46 Scott Moser nominated for series Ubuntu Xenial
2017-03-27 17:39:46 Scott Moser bug task added cloud-init (Ubuntu Xenial)
2017-03-27 17:39:46 Scott Moser bug task added nova-lxd (Ubuntu Xenial)
2017-03-27 17:40:05 Scott Moser cloud-init (Ubuntu Xenial): importance Undecided Medium
2017-03-27 17:40:05 Scott Moser cloud-init (Ubuntu Xenial): status New Confirmed
2017-03-27 17:40:22 Scott Moser cloud-init (Ubuntu Yakkety): importance Undecided Medium
2017-03-27 17:40:22 Scott Moser cloud-init (Ubuntu Yakkety): status New Confirmed
2017-03-27 17:40:42 Scott Moser cloud-init (Ubuntu Zesty): importance Undecided Medium
2017-03-27 17:40:42 Scott Moser cloud-init (Ubuntu Zesty): status New Fix Released
2017-04-05 12:55:11 James Page nova-lxd (Ubuntu Xenial): status New Invalid
2017-04-05 12:55:35 James Page bug task added cloud-archive
2017-04-05 12:55:48 James Page nominated for series cloud-archive/newton
2017-04-05 12:55:48 James Page bug task added cloud-archive/newton
2017-04-05 12:55:48 James Page nominated for series cloud-archive/ocata
2017-04-05 12:55:48 James Page bug task added cloud-archive/ocata
2017-04-05 12:55:59 James Page cloud-archive/newton: status New Triaged
2017-04-05 12:56:09 James Page cloud-archive/ocata: status New Triaged
2017-04-05 15:48:29 Chuck Short nova-lxd (Ubuntu Zesty): status Triaged Fix Committed
2017-04-05 16:21:02 Scott Moser description 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). http://pad.lv/1673411 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1673411 === 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' ## and push it to the container $ d=$(mktemp -d) $ make-config-drive "$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).
2017-04-05 16:21:55 Scott Moser description http://pad.lv/1673411 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1673411 === 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' ## and push it to the container $ d=$(mktemp -d) $ make-config-drive "$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). http://pad.lv/1673411 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1673411 === 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).
2017-04-05 16:22:40 Scott Moser attachment added make-configdrive-dir (referenced in cloud-init sru) https://bugs.launchpad.net/nova-lxd/+bug/1673411/+attachment/4855475/+files/make-configdrive-dir
2017-04-05 16:22:59 Scott Moser description http://pad.lv/1673411 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1673411 === 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). === 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).
2017-04-10 22:24:11 Brian Murray cloud-init (Ubuntu Yakkety): status Confirmed Fix Committed
2017-04-10 22:24:15 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2017-04-10 22:24:21 Brian Murray bug added subscriber SRU Verification
2017-04-10 22:24:29 Brian Murray tags verification-needed
2017-04-10 22:46:54 Brian Murray cloud-init (Ubuntu Xenial): status Confirmed Fix Committed
2017-04-13 20:02:21 Andreas Hasenack tags verification-needed verification-done-yakkety verification-needed
2017-04-13 20:29:01 Andreas Hasenack tags verification-done-yakkety verification-needed verification-done-xenial verification-done-yakkety verification-needed
2017-04-13 20:38:47 Andreas Hasenack tags verification-done-xenial verification-done-yakkety verification-needed verification-done-xenial verification-done-yakkety
2017-04-20 19:33:34 Launchpad Janitor cloud-init (Ubuntu Yakkety): status Fix Committed Fix Released
2017-04-20 19:34:44 Steve Langasek removed subscriber Ubuntu Stable Release Updates Team
2017-04-20 19:35:54 Launchpad Janitor cloud-init (Ubuntu Xenial): status Fix Committed Fix Released
2017-04-26 11:22:23 James Page nova-lxd (Ubuntu): status Fix Committed Fix Released
2017-04-26 11:22:53 James Page nova-lxd (Ubuntu Zesty): status Fix Committed Fix Released
2017-04-26 11:23:09 James Page cloud-archive/ocata: status Triaged Fix Released
2017-04-26 11:24:14 James Page bug added subscriber Ubuntu Stable Release Updates Team
2017-05-04 21:21:18 Brian Murray nova-lxd (Ubuntu Yakkety): status Triaged Fix Committed
2017-05-04 21:21:30 Brian Murray tags verification-done-xenial verification-done-yakkety verification-done-xenial verification-done-yakkety verification-needed
2017-05-15 08:50:50 James Page cloud-archive/newton: status Triaged Fix Committed
2017-05-15 08:50:52 James Page tags verification-done-xenial verification-done-yakkety verification-needed verification-done-xenial verification-done-yakkety verification-needed verification-newton-needed
2017-05-17 09:47:46 James Page nova-lxd/newton: status Fix Committed Fix Released
2017-05-17 09:48:02 James Page nova-lxd/ocata: status Fix Committed Fix Released
2017-05-17 09:48:19 James Page tags verification-done-xenial verification-done-yakkety verification-needed verification-newton-needed verification-done-xenial verification-done-yakkety verification-needed verification-newton-failed
2017-05-17 09:48:33 James Page tags verification-done-xenial verification-done-yakkety verification-needed verification-newton-failed verification-done-xenial verification-done-yakkety verification-failed verification-newton-failed
2017-05-18 20:31:05 Brian Murray tags verification-done-xenial verification-done-yakkety verification-failed verification-newton-failed verification-done-xenial verification-done-yakkety verification-newton-failed
2017-05-18 20:31:08 Brian Murray tags verification-done-xenial verification-done-yakkety verification-newton-failed verification-done-xenial verification-done-yakkety verification-needed verification-newton-failed
2017-05-19 13:49:01 James Page tags verification-done-xenial verification-done-yakkety verification-needed verification-newton-failed verification-done-xenial verification-done-yakkety verification-needed verification-yakkety-done
2017-05-19 13:50:03 James Page tags verification-done-xenial verification-done-yakkety verification-needed verification-yakkety-done verification-done verification-done-xenial verification-done-yakkety
2017-05-25 22:30:19 Launchpad Janitor nova-lxd (Ubuntu Yakkety): status Fix Committed Fix Released
2017-06-01 16:59:27 James Page cloud-archive/newton: status Fix Committed Fix Released
2017-09-23 02:29:43 Scott Moser cloud-init: status Fix Committed Fix Released
2023-05-10 21:47:29 James Falcon bug watch added https://github.com/canonical/cloud-init/issues/2828