| Thread Previous • Date Previous • Date Next • Thread Next |
Public bug reported:
For instance booted from volume with legacy bdm and image (this method is documented as workaround in http://docs.openstack.org/grizzly/openstack-ops/content/attach_block_storage.html) admin user creates instance snapshot in the image tenant rather than current tenant.
Created snapshot cannot be used.
Environment: DevStack
Steps to reproduce:
1 Create bootable volume from public image from not current tenant.
For example, use demo tenant in DevStack.
$ cinder create --image-id xxx 1
Note: I used cirros-0.3.2-x86_64-uec ami image.
2 Boot an instance from the volume passing the original image.
$ nova boot --flavor m1.nano --image xxx --block-device-mapping /dev/vda=yyy inst
3 Create instance snapshot under admin user
$ nova image-create inst snap
4 List images and make sure there is no the created snapshot.
$ glance image-list
5 List images from the original image tenant and found the snapshot.
$ glance --os-tenant-name nnn image-list
snapshot_volume_backed in nova/compute/api.py receives image in image_meta parameter, cleans some attributes, but forgets to deal something with owner attribute.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1322195
Title:
Admin creates volume backed instance snapshot in image tenant
Status in OpenStack Compute (Nova):
New
Bug description:
For instance booted from volume with legacy bdm and image (this method is documented as workaround in http://docs.openstack.org/grizzly/openstack-ops/content/attach_block_storage.html) admin user creates instance snapshot in the image tenant rather than current tenant.
Created snapshot cannot be used.
Environment: DevStack
Steps to reproduce:
1 Create bootable volume from public image from not current tenant.
For example, use demo tenant in DevStack.
$ cinder create --image-id xxx 1
Note: I used cirros-0.3.2-x86_64-uec ami image.
2 Boot an instance from the volume passing the original image.
$ nova boot --flavor m1.nano --image xxx --block-device-mapping /dev/vda=yyy inst
3 Create instance snapshot under admin user
$ nova image-create inst snap
4 List images and make sure there is no the created snapshot.
$ glance image-list
5 List images from the original image tenant and found the snapshot.
$ glance --os-tenant-name nnn image-list
snapshot_volume_backed in nova/compute/api.py receives image in image_meta parameter, cleans some attributes, but forgets to deal something with owner attribute.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1322195/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
