Activity log for bug #1685810

Date Who What changed Old value New value Message
2017-04-24 14:26:03 Scott Moser bug added bug
2017-04-24 14:26:35 Scott Moser description It seems that signals were crossed in bug 1661797. cloud-init implementation reads the environment variable 'platform' from pid1, and nova-lxd implementation exported 'product_name'. Thus, ssh to nova-lxd provided container, user sees a warning. Also $ sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep PLAT PID_1_PLATFORM=unavailable Related bugs: * bug 1661797: identify lxd-nova platform to enable Openstack datasource It seems that signals were crossed in bug 1661797. cloud-init implementation reads the environment variable 'platform' from pid1, and nova-lxd implementation exported 'product_name'. Thus, ssh to nova-lxd provided container, user sees a warning. Also $ sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep PLAT PID_1_PLATFORM=unavailable While: $ sudo cat /proc/1/environ | tr '\0' '\n' product_name=OpenStack Nova container=lxc Related bugs:  * bug 1661797: identify lxd-nova platform to enable Openstack datasource
2017-04-24 17:23:00 Launchpad Janitor merge proposal linked https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/323057
2017-04-24 19:31:42 Scott Moser cloud-init: status Confirmed Fix Committed
2017-04-25 14:49:33 Scott Moser bug task added cloud-init (Ubuntu)
2017-04-25 14:49:39 Scott Moser cloud-init (Ubuntu): status New Confirmed
2017-04-25 14:49:41 Scott Moser cloud-init (Ubuntu): importance Undecided Medium
2017-04-25 14:49:49 Scott Moser nominated for series Ubuntu Zesty
2017-04-25 14:49:49 Scott Moser bug task added cloud-init (Ubuntu Zesty)
2017-04-25 14:49:49 Scott Moser nominated for series Ubuntu Xenial
2017-04-25 14:49:49 Scott Moser bug task added cloud-init (Ubuntu Xenial)
2017-04-25 14:49:49 Scott Moser nominated for series Ubuntu Yakkety
2017-04-25 14:49:49 Scott Moser bug task added cloud-init (Ubuntu Yakkety)
2017-04-25 14:50:25 Scott Moser cloud-init (Ubuntu Xenial): status New Confirmed
2017-04-25 14:50:27 Scott Moser cloud-init (Ubuntu Yakkety): status New Confirmed
2017-04-25 14:50:30 Scott Moser cloud-init (Ubuntu Zesty): status New Confirmed
2017-04-25 14:50:32 Scott Moser cloud-init (Ubuntu Xenial): importance Undecided Medium
2017-04-25 14:50:34 Scott Moser cloud-init (Ubuntu Yakkety): importance Undecided Medium
2017-04-25 14:50:37 Scott Moser cloud-init (Ubuntu Zesty): importance Undecided Medium
2017-04-26 01:30:48 Launchpad Janitor cloud-init (Ubuntu): status Confirmed Fix Released
2017-04-28 17:09:11 Chad Smith nominated for series Ubuntu Artful
2017-05-02 22:48:14 Chad Smith description It seems that signals were crossed in bug 1661797. cloud-init implementation reads the environment variable 'platform' from pid1, and nova-lxd implementation exported 'product_name'. Thus, ssh to nova-lxd provided container, user sees a warning. Also $ sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep PLAT PID_1_PLATFORM=unavailable While: $ sudo cat /proc/1/environ | tr '\0' '\n' product_name=OpenStack Nova container=lxc Related bugs:  * bug 1661797: identify lxd-nova platform to enable Openstack datasource === Begin SRU Template === [Impact] Warning message for nova-lxd images in openstack clouds due to no valid datasource found. [Test Case] # It downloads a cloud image of a given release, and then creates a -proposed image with cloud-init upgraded. wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot chmod 755 get-proposed-image source novarc for release in xenial yakkety zesty do; ref=$release-proposed; lxc-proposed-snapshot --proposed --publish $release $ref; lxc image export $ref .; imagefile=`ls -tr *gz | tail -n 1` mkdir $ref; cd $ref; tar -zxvf ../$imagefile; cd rootfs; tar zcvf $ref.tar.gz *; #upload raw image to your cloud openstack image create --disk-format raw --container-format bare --file $ref.tar.gz testing/$ref.tar.gz; openstack server create --image testing/$ref.tar.gz --flavor=m1.tiny lxd-$release --key-name <your-key>; nova floating-ip-create; nova foating-ip-associate <server> <address>; ssh ubuntu@<address> 'sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep Found'; # single datasource: OpenStack done [Regression Potential] Low as this only addresses the warning by correctly identifying the OpenStack cloud datasource. [Other Info] === End SRU Template === It seems that signals were crossed in bug 1661797. cloud-init implementation reads the environment variable 'platform' from pid1, and nova-lxd implementation exported 'product_name'. Thus, ssh to nova-lxd provided container, user sees a warning. Also $ sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep PLAT PID_1_PLATFORM=unavailable While: $ sudo cat /proc/1/environ | tr '\0' '\n' product_name=OpenStack Nova container=lxc Related bugs:  * bug 1661797: identify lxd-nova platform to enable Openstack datasource
2017-05-05 14:30:31 Scott Moser bug task added cloud-init (Ubuntu Artful)
2017-05-08 19:06:17 Steve Langasek cloud-init (Ubuntu Xenial): status Confirmed Fix Committed
2017-05-08 19:06:21 Steve Langasek bug added subscriber Ubuntu Stable Release Updates Team
2017-05-08 19:06:23 Steve Langasek bug added subscriber SRU Verification
2017-05-08 19:06:29 Steve Langasek tags dsid dsid verification-needed
2017-05-11 19:21:48 Chad Smith tags dsid verification-needed dsid verification-done-xenial verification-needed
2017-05-11 20:31:02 Steve Langasek cloud-init (Ubuntu Yakkety): status Confirmed Fix Committed
2017-05-11 20:37:54 Steve Langasek cloud-init (Ubuntu Zesty): status Confirmed Fix Committed
2017-05-12 18:17:44 Chad Smith description === Begin SRU Template === [Impact] Warning message for nova-lxd images in openstack clouds due to no valid datasource found. [Test Case] # It downloads a cloud image of a given release, and then creates a -proposed image with cloud-init upgraded. wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot chmod 755 get-proposed-image source novarc for release in xenial yakkety zesty do; ref=$release-proposed; lxc-proposed-snapshot --proposed --publish $release $ref; lxc image export $ref .; imagefile=`ls -tr *gz | tail -n 1` mkdir $ref; cd $ref; tar -zxvf ../$imagefile; cd rootfs; tar zcvf $ref.tar.gz *; #upload raw image to your cloud openstack image create --disk-format raw --container-format bare --file $ref.tar.gz testing/$ref.tar.gz; openstack server create --image testing/$ref.tar.gz --flavor=m1.tiny lxd-$release --key-name <your-key>; nova floating-ip-create; nova foating-ip-associate <server> <address>; ssh ubuntu@<address> 'sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep Found'; # single datasource: OpenStack done [Regression Potential] Low as this only addresses the warning by correctly identifying the OpenStack cloud datasource. [Other Info] === End SRU Template === It seems that signals were crossed in bug 1661797. cloud-init implementation reads the environment variable 'platform' from pid1, and nova-lxd implementation exported 'product_name'. Thus, ssh to nova-lxd provided container, user sees a warning. Also $ sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep PLAT PID_1_PLATFORM=unavailable While: $ sudo cat /proc/1/environ | tr '\0' '\n' product_name=OpenStack Nova container=lxc Related bugs:  * bug 1661797: identify lxd-nova platform to enable Openstack datasource === Begin SRU Template === [Impact] Warning message for nova-lxd images in openstack clouds due to no valid datasource found. [Test Case] # It downloads a cloud image of a given release, and then creates a -proposed image with cloud-init upgraded. wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot chmod 755 get-proposed-image source novarc for release in xenial yakkety zesty do;  ref=$release-proposed;  lxc-proposed-snapshot --proposed --publish $release $ref;  lxc image export $ref .;  imagefile=`ls -tr *gz | tail -n 1`  mkdir $ref;  cd $ref;  sudo tar -zxvpf ../$imagefile; # preserve permissions  cd rootfs;  sudo tar zcpvf $ref.tar.gz *;  #upload raw image to your cloud   openstack image create --disk-format raw --container-format bare --file $ref.tar.gz testing/$ref.tar.gz;   openstack server create --image testing/$ref.tar.gz --flavor=m1.tiny lxd-$release --key-name <your-key>;   nova floating-ip-create;   nova foating-ip-associate <server> <address>;   ssh ubuntu@<address> 'sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep Found'; # single datasource: OpenStack done [Regression Potential] Low as this only addresses the warning by correctly identifying the OpenStack cloud datasource. [Other Info] === End SRU Template === It seems that signals were crossed in bug 1661797. cloud-init implementation reads the environment variable 'platform' from pid1, and nova-lxd implementation exported 'product_name'. Thus, ssh to nova-lxd provided container, user sees a warning. Also $ sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 2>&1 | grep PLAT PID_1_PLATFORM=unavailable While: $ sudo cat /proc/1/environ | tr '\0' '\n' product_name=OpenStack Nova container=lxc Related bugs:  * bug 1661797: identify lxd-nova platform to enable Openstack datasource
2017-05-12 18:27:05 Chad Smith tags dsid verification-done-xenial verification-needed dsid verification-done-xenial verification-done-yakkety verification-done-zesty
2017-05-17 02:58:17 Launchpad Janitor cloud-init (Ubuntu Xenial): status Fix Committed Fix Released
2017-05-17 02:59:12 Chris Halse Rogers removed subscriber Ubuntu Stable Release Updates Team
2017-05-17 03:07:38 Launchpad Janitor cloud-init (Ubuntu Yakkety): status Fix Committed Fix Released
2017-05-17 03:14:07 Launchpad Janitor cloud-init (Ubuntu Zesty): status Fix Committed Fix Released
2017-09-23 02:31:28 Scott Moser cloud-init: status Fix Committed Fix Released
2023-05-10 23:51:58 James Falcon bug watch added https://github.com/canonical/cloud-init/issues/2866