yahoo-eng-team team mailing list archive

[Timur Nurlygayanov <tnurlygayanov@xxxxxxxxxxxx>]

Not reproduced, looks like some configuration issue on my previous lab.

** Changed in: nova
       Status: Incomplete => Invalid

-- 
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/1490528

Title:
  Strange logic for shared images for different tenants/users

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Nova version: 1:2015.1.1-1 (OpenStack Kilo release)

  Steps To Reproduce:
  1. Login to OpenStack horizon dashboard as admin user
  2. Upload Ubuntu cloud image into Glance
  3. Boot VM 'test1' from Ubuntu image
  4. Install stress tool on the VM: 'sudo apt-get install stress'
  5. Add 'stress' tool in autorun: 'sudo echo "stress --cpu 10 &" > /etc/rc.local'
  6. Reboot VM 'test1'
  7. Make a snapshot of 'test1' VM
  8. Mark this snapshot as 'public' in Glance
  9. Create 10 VMs with this image (snapshot) from admin user. All VMs became Active in several seconds.
  10. Login as non-admin user in another tenant (for example, user 'test' in tenant 'my-project')
  11. Boot 10 VMs with public image 'TestImage'

  Expected Result:
  VMs will start as quickly as for the admin tenant.

  Observed Result:
  VMs hang in "Downloading Image" operation, it takes more than 20 minutes to run VM from the snapshot in other tenants (but in the same time it takes a few seconds to run VMs from the same image from tenant where we have created the image).

  Looks like Nova tries to copy this image for each new tenant, and it
  doesn't looks correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1490528/+subscriptions