| 2012-08-16 13:20:44 |
Scott Moser |
bug |
|
|
added bug |
| 2012-08-16 13:50:35 |
Scott Moser |
cloud-init: status |
New |
Triaged |
|
| 2012-08-16 13:50:38 |
Scott Moser |
cloud-init: importance |
Undecided |
Medium |
|
| 2012-08-24 21:23:16 |
Launchpad Janitor |
branch linked |
|
lp:cloud-init |
|
| 2012-08-24 21:25:20 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/cloud-init |
|
| 2012-08-27 12:43:32 |
Scott Moser |
cloud-init: status |
Triaged |
Fix Committed |
|
| 2012-10-01 18:25:18 |
Scott Moser |
cloud-init: status |
Fix Committed |
Fix Released |
|
| 2012-11-12 17:42:23 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu) |
|
| 2012-11-12 17:42:41 |
Scott Moser |
nominated for series |
|
Ubuntu Precise |
|
| 2012-11-12 17:42:41 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Precise) |
|
| 2012-11-12 17:42:41 |
Scott Moser |
nominated for series |
|
Ubuntu Quantal |
|
| 2012-11-12 17:42:41 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Quantal) |
|
| 2012-11-12 17:42:50 |
Scott Moser |
cloud-init (Ubuntu Quantal): status |
New |
Fix Released |
|
| 2012-11-12 17:42:52 |
Scott Moser |
cloud-init (Ubuntu Quantal): importance |
Undecided |
Medium |
|
| 2012-11-12 17:43:01 |
Scott Moser |
cloud-init (Ubuntu Precise): status |
New |
Triaged |
|
| 2012-11-12 17:43:06 |
Scott Moser |
cloud-init (Ubuntu Precise): importance |
Undecided |
High |
|
| 2012-11-12 17:43:10 |
Scott Moser |
cloud-init (Ubuntu): status |
New |
Fix Released |
|
| 2012-11-12 17:43:14 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
Medium |
|
| 2013-01-09 17:49:31 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/precise/cloud-init/sru |
|
| 2013-01-14 01:52:22 |
Scott Moser |
bug |
|
|
added subscriber Alessandro Pilotti |
| 2013-01-31 19:29:22 |
Scott Moser |
attachment added |
|
example config drive disk (iso) https://bugs.launchpad.net/cloud-init/+bug/1037567/+attachment/3509468/+files/disk.config.gz |
|
| 2013-01-31 19:36:39 |
Scott Moser |
description |
We need to update the config-drive datasource to support config-drive-v2 [1]. There is a document showing what the config-drive looks like at [2].
[1] https://blueprints.launchpad.net/nova/+spec/config-drive-v2
[2] http://paste.ubuntu.com/1150619/ |
== Begin SRU Information ==
[Impact]
'config-drive' is a mechanism for passing data from the hypervisor (or
cloud platform) to the guest (instance). config-drive-v2 was implemented
in Openstack Folsom release, and delivered as functional in 12.10 Ubuntu.
In order to support Ubuntu 12.04 cloud images running as a guest on
Openstack clouds that utilize config-drive, we need to backport this
function to 12.04.
This feature backport can be considered "hardware enablement" as it
enables Ubuntu images to work on new cloud platforms.
[Test Case]
Attached to this bug is an ISO that provides config-drive-v2 data.
Currently, if you attach the ISO to a cloud-image instance,
it will be ignored.
The new version of cloud-init enables data to be read from the disk.
The provided ISO file simply sets a password for the 'ubuntu' user to
'ubuntu'. So, verification that the test worked is as easy as logging
in with 'ubuntu' and 'passw0rd', either via ssh or via the console.
Additionally, when the config-drive is not found, cloud-init will fall
back to the EC2 data source, and block boot for several minutes as it
waits. When the config-drive is found, boot will occur quickly.
To perform this test, download a precise cloud-image from
http://cloud-images.ubuntu.com patch it, and boot it with kvm.
$ imgurl="http://cloud-images.ubuntu.com/releases/precise/release-20130124/ubuntu-12.04-server-cloudimg-amd64-disk1.img"
$ deburl="wget https://launchpad.net/~smoser/+archive/cloud-init-test/+files/cloud-init_0.6.3-0ubuntu1.5%7Eppa1_all.deb"
$ isourl="https://bugs.launchpad.net/cloud-init/+bug/1037567/+attachment/3509468/+files/disk.config.gz"
$ wget $url -O precise-amd64.img.dist
$ wget $deburl -O cloud-init.deb
$ wget $isourl -O cfgdisk.img.dist;
$ qemu-img convert -O qcow2 precise-amd64.img.dist disk1.img.dist
$ qemu-img create -f qcow2 -b disk1.img.dist patched.img.dist
$ zcat --force cfgdisk.img.dist > cfgdisk.img
$ chmod 600 cfgdisk.img disk1.img.dist
# patch the patched.img.dist with new cloud-init
$ bzr branch lp:~smoser/+junk/backdoor-image ./bi
$ sudo ./bi/mount-callback-umount patched.img.dist -- \
sh -ec 'mp=$1; cp cloud-init.deb $mp/tmp &&
LANG=C chroot $mp dpkg -i /tmp/cloud-init.deb ;
rm $mp/tmp/cloud-init.deb' --
$ qemu-img create -f qcow2 -b disk1.img.dist unpatched.img
$ qemu-img create -f qcow2 -b patched.img.dist patched.img
# boot patched and unpatched images
$ kvm -m 512 -drive file=unpatched.img,if=virtio -drive file=cfgdisk.img,if=virtio
$ kvm -m 512 -drive file=patched.img,if=virtio -drive file=cfgdisk.img,if=virtio
The unpatched version will take quite a long time to boot, and you'll messages
on the serial console like:see:
2013-01-31 18:53:18,185 - DataSourceEc2.py[CRITICAL]: giving up on md after 120
Booting a kvm instance with iso as cdrom:
kvm -drive disk1.img,if=virtio -cdrom lp-1077020.iso
Booting a kvm instance with iso as disk:
kvm -drive disk1.img,if=virtio -drive lp-1077020.iso,if=virtio lp-1077020.iso
[Regression Potential]
The potential for regression is low. The most likely possibility for
error would be in incorrectly identifying a cd-rom and its content as a
config-drive.
== End SRU Information ==
## Howto launch instance with config-drive ###
nova keypair-add --pub-key ~/.ssh/id_rsa.pub mykey
nova boot --key_name=mykey --image=$IMAGE \
--config-drive=1 --flavor=m1.tiny \
--user_data=./user-data.txt cfg-drive-test
We need to update the config-drive datasource to support config-drive-v2 [1]. There is a document showing what the config-drive looks like at [2].
[1] https://blueprints.launchpad.net/nova/+spec/config-drive-v2
[2] http://paste.ubuntu.com/1150619/ |
|
| 2013-01-31 19:37:20 |
Scott Moser |
description |
== Begin SRU Information ==
[Impact]
'config-drive' is a mechanism for passing data from the hypervisor (or
cloud platform) to the guest (instance). config-drive-v2 was implemented
in Openstack Folsom release, and delivered as functional in 12.10 Ubuntu.
In order to support Ubuntu 12.04 cloud images running as a guest on
Openstack clouds that utilize config-drive, we need to backport this
function to 12.04.
This feature backport can be considered "hardware enablement" as it
enables Ubuntu images to work on new cloud platforms.
[Test Case]
Attached to this bug is an ISO that provides config-drive-v2 data.
Currently, if you attach the ISO to a cloud-image instance,
it will be ignored.
The new version of cloud-init enables data to be read from the disk.
The provided ISO file simply sets a password for the 'ubuntu' user to
'ubuntu'. So, verification that the test worked is as easy as logging
in with 'ubuntu' and 'passw0rd', either via ssh or via the console.
Additionally, when the config-drive is not found, cloud-init will fall
back to the EC2 data source, and block boot for several minutes as it
waits. When the config-drive is found, boot will occur quickly.
To perform this test, download a precise cloud-image from
http://cloud-images.ubuntu.com patch it, and boot it with kvm.
$ imgurl="http://cloud-images.ubuntu.com/releases/precise/release-20130124/ubuntu-12.04-server-cloudimg-amd64-disk1.img"
$ deburl="wget https://launchpad.net/~smoser/+archive/cloud-init-test/+files/cloud-init_0.6.3-0ubuntu1.5%7Eppa1_all.deb"
$ isourl="https://bugs.launchpad.net/cloud-init/+bug/1037567/+attachment/3509468/+files/disk.config.gz"
$ wget $url -O precise-amd64.img.dist
$ wget $deburl -O cloud-init.deb
$ wget $isourl -O cfgdisk.img.dist;
$ qemu-img convert -O qcow2 precise-amd64.img.dist disk1.img.dist
$ qemu-img create -f qcow2 -b disk1.img.dist patched.img.dist
$ zcat --force cfgdisk.img.dist > cfgdisk.img
$ chmod 600 cfgdisk.img disk1.img.dist
# patch the patched.img.dist with new cloud-init
$ bzr branch lp:~smoser/+junk/backdoor-image ./bi
$ sudo ./bi/mount-callback-umount patched.img.dist -- \
sh -ec 'mp=$1; cp cloud-init.deb $mp/tmp &&
LANG=C chroot $mp dpkg -i /tmp/cloud-init.deb ;
rm $mp/tmp/cloud-init.deb' --
$ qemu-img create -f qcow2 -b disk1.img.dist unpatched.img
$ qemu-img create -f qcow2 -b patched.img.dist patched.img
# boot patched and unpatched images
$ kvm -m 512 -drive file=unpatched.img,if=virtio -drive file=cfgdisk.img,if=virtio
$ kvm -m 512 -drive file=patched.img,if=virtio -drive file=cfgdisk.img,if=virtio
The unpatched version will take quite a long time to boot, and you'll messages
on the serial console like:see:
2013-01-31 18:53:18,185 - DataSourceEc2.py[CRITICAL]: giving up on md after 120
Booting a kvm instance with iso as cdrom:
kvm -drive disk1.img,if=virtio -cdrom lp-1077020.iso
Booting a kvm instance with iso as disk:
kvm -drive disk1.img,if=virtio -drive lp-1077020.iso,if=virtio lp-1077020.iso
[Regression Potential]
The potential for regression is low. The most likely possibility for
error would be in incorrectly identifying a cd-rom and its content as a
config-drive.
== End SRU Information ==
## Howto launch instance with config-drive ###
nova keypair-add --pub-key ~/.ssh/id_rsa.pub mykey
nova boot --key_name=mykey --image=$IMAGE \
--config-drive=1 --flavor=m1.tiny \
--user_data=./user-data.txt cfg-drive-test
We need to update the config-drive datasource to support config-drive-v2 [1]. There is a document showing what the config-drive looks like at [2].
[1] https://blueprints.launchpad.net/nova/+spec/config-drive-v2
[2] http://paste.ubuntu.com/1150619/ |
== Begin SRU Information ==
[Impact]
'config-drive' is a mechanism for passing data from the hypervisor (or
cloud platform) to the guest (instance). config-drive-v2 was implemented
in Openstack Folsom release, and delivered as functional in 12.10 Ubuntu.
In order to support Ubuntu 12.04 cloud images running as a guest on
Openstack clouds that utilize config-drive, we need to backport this
function to 12.04.
This feature backport can be considered "hardware enablement" as it
enables Ubuntu images to work on new cloud platforms.
[Test Case]
Attached to this bug is an ISO that provides config-drive-v2 data.
Currently, if you attach the ISO to a cloud-image instance,
it will be ignored.
The new version of cloud-init enables data to be read from the disk.
The provided ISO file simply sets a password for the 'ubuntu' user to
'ubuntu'. So, verification that the test worked is as easy as logging
in with 'ubuntu' and 'passw0rd', either via ssh or via the console.
Additionally, when the config-drive is not found, cloud-init will fall
back to the EC2 data source, and block boot for several minutes as it
waits. When the config-drive is found, boot will occur quickly.
To perform this test, download a precise cloud-image from
http://cloud-images.ubuntu.com patch it, and boot it with kvm.
$ imgurl="http://cloud-images.ubuntu.com/releases/precise/release-20130124/ubuntu-12.04-server-cloudimg-amd64-disk1.img"
$ deburl="wget https://launchpad.net/~smoser/+archive/cloud-init-test/+files/cloud-init_0.6.3-0ubuntu1.5%7Eppa1_all.deb"
$ isourl="https://bugs.launchpad.net/cloud-init/+bug/1037567/+attachment/3509468/+files/disk.config.gz"
$ wget $url -O precise-amd64.img.dist
$ wget $deburl -O cloud-init.deb
$ wget $isourl -O cfgdisk.img.dist;
$ qemu-img convert -O qcow2 precise-amd64.img.dist disk1.img.dist
$ qemu-img create -f qcow2 -b disk1.img.dist patched.img.dist
$ zcat --force cfgdisk.img.dist > cfgdisk.img
$ chmod 600 cfgdisk.img disk1.img.dist
# patch the patched.img.dist with new cloud-init
$ bzr branch lp:~smoser/+junk/backdoor-image ./bi
$ sudo ./bi/mount-callback-umount patched.img.dist -- \
sh -ec 'mp=$1; cp cloud-init.deb $mp/tmp &&
LANG=C chroot $mp dpkg -i /tmp/cloud-init.deb ;
rm $mp/tmp/cloud-init.deb' --
$ qemu-img create -f qcow2 -b disk1.img.dist unpatched.img
$ qemu-img create -f qcow2 -b patched.img.dist patched.img
# boot patched and unpatched images
$ kvm -m 512 -drive file=unpatched.img,if=virtio -drive file=cfgdisk.img,if=virtio
$ kvm -m 512 -drive file=patched.img,if=virtio -drive file=cfgdisk.img,if=virtio
The unpatched version will take quite a long time to boot, and you'll messages
on the serial console like:see:
2013-01-31 18:53:18,185 - DataSourceEc2.py[CRITICAL]: giving up on md after 120
[Regression Potential]
The potential for regression is low. The most likely possibility for
error would be in incorrectly identifying a cd-rom and its content as a
config-drive.
== End SRU Information ==
## Howto launch instance with config-drive ###
nova keypair-add --pub-key ~/.ssh/id_rsa.pub mykey
nova boot --key_name=mykey --image=$IMAGE \
--config-drive=1 --flavor=m1.tiny \
--user_data=./user-data.txt cfg-drive-test
We need to update the config-drive datasource to support config-drive-v2 [1]. There is a document showing what the config-drive looks like at [2].
[1] https://blueprints.launchpad.net/nova/+spec/config-drive-v2
[2] http://paste.ubuntu.com/1150619/ |
|
| 2013-01-31 19:54:31 |
Scott Moser |
description |
== Begin SRU Information ==
[Impact]
'config-drive' is a mechanism for passing data from the hypervisor (or
cloud platform) to the guest (instance). config-drive-v2 was implemented
in Openstack Folsom release, and delivered as functional in 12.10 Ubuntu.
In order to support Ubuntu 12.04 cloud images running as a guest on
Openstack clouds that utilize config-drive, we need to backport this
function to 12.04.
This feature backport can be considered "hardware enablement" as it
enables Ubuntu images to work on new cloud platforms.
[Test Case]
Attached to this bug is an ISO that provides config-drive-v2 data.
Currently, if you attach the ISO to a cloud-image instance,
it will be ignored.
The new version of cloud-init enables data to be read from the disk.
The provided ISO file simply sets a password for the 'ubuntu' user to
'ubuntu'. So, verification that the test worked is as easy as logging
in with 'ubuntu' and 'passw0rd', either via ssh or via the console.
Additionally, when the config-drive is not found, cloud-init will fall
back to the EC2 data source, and block boot for several minutes as it
waits. When the config-drive is found, boot will occur quickly.
To perform this test, download a precise cloud-image from
http://cloud-images.ubuntu.com patch it, and boot it with kvm.
$ imgurl="http://cloud-images.ubuntu.com/releases/precise/release-20130124/ubuntu-12.04-server-cloudimg-amd64-disk1.img"
$ deburl="wget https://launchpad.net/~smoser/+archive/cloud-init-test/+files/cloud-init_0.6.3-0ubuntu1.5%7Eppa1_all.deb"
$ isourl="https://bugs.launchpad.net/cloud-init/+bug/1037567/+attachment/3509468/+files/disk.config.gz"
$ wget $url -O precise-amd64.img.dist
$ wget $deburl -O cloud-init.deb
$ wget $isourl -O cfgdisk.img.dist;
$ qemu-img convert -O qcow2 precise-amd64.img.dist disk1.img.dist
$ qemu-img create -f qcow2 -b disk1.img.dist patched.img.dist
$ zcat --force cfgdisk.img.dist > cfgdisk.img
$ chmod 600 cfgdisk.img disk1.img.dist
# patch the patched.img.dist with new cloud-init
$ bzr branch lp:~smoser/+junk/backdoor-image ./bi
$ sudo ./bi/mount-callback-umount patched.img.dist -- \
sh -ec 'mp=$1; cp cloud-init.deb $mp/tmp &&
LANG=C chroot $mp dpkg -i /tmp/cloud-init.deb ;
rm $mp/tmp/cloud-init.deb' --
$ qemu-img create -f qcow2 -b disk1.img.dist unpatched.img
$ qemu-img create -f qcow2 -b patched.img.dist patched.img
# boot patched and unpatched images
$ kvm -m 512 -drive file=unpatched.img,if=virtio -drive file=cfgdisk.img,if=virtio
$ kvm -m 512 -drive file=patched.img,if=virtio -drive file=cfgdisk.img,if=virtio
The unpatched version will take quite a long time to boot, and you'll messages
on the serial console like:see:
2013-01-31 18:53:18,185 - DataSourceEc2.py[CRITICAL]: giving up on md after 120
[Regression Potential]
The potential for regression is low. The most likely possibility for
error would be in incorrectly identifying a cd-rom and its content as a
config-drive.
== End SRU Information ==
## Howto launch instance with config-drive ###
nova keypair-add --pub-key ~/.ssh/id_rsa.pub mykey
nova boot --key_name=mykey --image=$IMAGE \
--config-drive=1 --flavor=m1.tiny \
--user_data=./user-data.txt cfg-drive-test
We need to update the config-drive datasource to support config-drive-v2 [1]. There is a document showing what the config-drive looks like at [2].
[1] https://blueprints.launchpad.net/nova/+spec/config-drive-v2
[2] http://paste.ubuntu.com/1150619/ |
== Begin SRU Information ==
[Impact]
'config-drive' is a mechanism for passing data from the hypervisor (or
cloud platform) to the guest (instance). config-drive-v2 was implemented
in Openstack Folsom release, and delivered as functional in 12.10 Ubuntu.
In order to support Ubuntu 12.04 cloud images running as a guest on
Openstack clouds that utilize config-drive, we need to backport this
function to 12.04.
This feature backport can be considered "hardware enablement" as it
enables Ubuntu images to work on new cloud platforms.
[Test Case]
Attached to this bug is an ISO that provides config-drive-v2 data.
Currently, if you attach the ISO to a cloud-image instance,
it will be ignored.
The new version of cloud-init enables data to be read from the disk.
The provided ISO file simply sets a password for the 'ubuntu' user to
'ubuntu'. So, verification that the test worked is as easy as logging
in with 'ubuntu' and 'passw0rd', either via ssh or via the console.
Additionally, when the config-drive is not found, cloud-init will fall
back to the EC2 data source, and block boot for several minutes as it
waits. When the config-drive is found, boot will occur quickly.
To perform this test, download a precise cloud-image from
http://cloud-images.ubuntu.com patch it, and boot it with kvm.
$ imgurl="http://cloud-images.ubuntu.com/releases/precise/release-20130124/ubuntu-12.04-server-cloudimg-amd64-disk1.img"
$ deburl="https://launchpad.net/~smoser/+archive/cloud-init-test/+files/cloud-init_0.6.3-0ubuntu1.5%7Eppa1_all.deb"
$ isourl="https://bugs.launchpad.net/cloud-init/+bug/1037567/+attachment/3509468/+files/disk.config.gz"
$ wget $imgurl -O precise-amd64.img.dist
$ wget $deburl -O cloud-init.deb
$ wget $isourl -O cfgdisk.img.dist;
$ qemu-img convert -O qcow2 precise-amd64.img.dist disk1.img.dist
$ qemu-img create -f qcow2 -b disk1.img.dist patched.img.dist
$ zcat --force cfgdisk.img.dist > cfgdisk.img
$ chmod 600 cfgdisk.img disk1.img.dist
# patch the patched.img.dist with new cloud-init
$ bzr branch lp:~smoser/+junk/backdoor-image ./bi
$ sudo ./bi/mount-callback-umount patched.img.dist -- \
sh -ec 'mp=$1; cp cloud-init.deb $mp/tmp &&
LANG=C chroot $mp dpkg -i /tmp/cloud-init.deb ;
rm $mp/tmp/cloud-init.deb' --
$ qemu-img create -f qcow2 -b disk1.img.dist unpatched.img
$ qemu-img create -f qcow2 -b patched.img.dist patched.img
# boot patched and unpatched images
$ kvm -m 512 -drive file=unpatched.img,if=virtio -drive file=cfgdisk.img,if=virtio
$ kvm -m 512 -drive file=patched.img,if=virtio -drive file=cfgdisk.img,if=virtio
The unpatched version will take quite a long time to boot, and you'll messages
on the serial console like:see:
2013-01-31 18:53:18,185 - DataSourceEc2.py[CRITICAL]: giving up on md after 120
[Regression Potential]
The potential for regression is low. The most likely possibility for
error would be in incorrectly identifying a cd-rom and its content as a
config-drive.
== End SRU Information ==
## Howto launch instance with config-drive ###
nova keypair-add --pub-key ~/.ssh/id_rsa.pub mykey
nova boot --key_name=mykey --image=$IMAGE \
--config-drive=1 --flavor=m1.tiny \
--user_data=./user-data.txt cfg-drive-test
We need to update the config-drive datasource to support config-drive-v2 [1]. There is a document showing what the config-drive looks like at [2].
[1] https://blueprints.launchpad.net/nova/+spec/config-drive-v2 |
|
| 2013-02-19 18:27:19 |
Clint Byrum |
cloud-init (Ubuntu Precise): status |
Triaged |
Fix Committed |
|
| 2013-02-19 18:27:24 |
Clint Byrum |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2013-02-19 18:27:29 |
Clint Byrum |
bug |
|
|
added subscriber SRU Verification |
| 2013-02-19 18:27:34 |
Clint Byrum |
tags |
|
verification-needed |
|
| 2013-02-19 21:46:04 |
Scott Moser |
tags |
verification-needed |
verification-done |
|
| 2013-02-27 02:42:32 |
Colin Watson |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2013-02-27 02:43:11 |
Launchpad Janitor |
cloud-init (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
| 2013-08-28 11:32:39 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/precise/cloud-init/precise-proposed |
|
| 2013-08-28 11:32:56 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/precise/cloud-init/precise-updates |
|
| 2023-05-09 21:30:00 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2281 |
|
