← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1380617] [NEW] In-consistence behaviour for unshelve if snapshot and image is deleted from glance

 

Public bug reported:

In-consistence behaviour for unshelve if snapshot and image is deleted
from glance

When the instance is shelved it creates the instance snapshot in the glance.
If the instance snapshot and the image from which instance is created is deleted then unshelving the instance in the first try gives the error 'ImageNotFound', and in second try the unshelve completes successfully and instance goes in the active state.

Steps to reproduce:
1. create instance, wait until it becomes active.
2. shelve the instance 
$ nova shelve <instance_id or instance_name>

3. A snapshot is created and uploaded to glance.
4. Delete the snapshot and the image from which instance is created in the 1st step. (using admin credentials)
5. unshelve the instance
$ nova unshelve <instance_id or instance_name>

6. Stack trace is printed on screen logs:

nova-copute log:
   ImageNotFound: Image 442ea9bb-b664-41b4-b38b-8f5a690998d6 could not be found.

glance-api log:
   2014-10-10 04:02:49.007 4546 DEBUG glance.api.v1.controller [-] Image 476b81bc-d1b1-40db-bad8-4f37ae3c66ac is not active 
get_active_image_meta_or_404 /opt/stack/glance/glance/api/v1/controller.py:61
   2014-10-10 04:02:49.008 4546 INFO glance.wsgi.server [-] 10.69.4.130 - - [10/Oct/2014 04:02:49]
"GET /v1/images/476b81bc-d1b1-40db-bad8-4f37ae3c66ac HTTP/1.1" 404 400 0.121644

7. Once again unshelve the same instance.
$ nova unshelve <instance_id or instance_name>

8. This time you can not see the stack trace and instance goes in the active state successfully.
9. When I use nova show command, it shows that instance is booted from the same image which is used in step #1.

I have tested this scenario in the single node deployment.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: ntt

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

Title:
  In-consistence behaviour for unshelve if snapshot and image is deleted
  from glance

Status in OpenStack Compute (Nova):
  New

Bug description:
  In-consistence behaviour for unshelve if snapshot and image is deleted
  from glance

  When the instance is shelved it creates the instance snapshot in the glance.
  If the instance snapshot and the image from which instance is created is deleted then unshelving the instance in the first try gives the error 'ImageNotFound', and in second try the unshelve completes successfully and instance goes in the active state.

  Steps to reproduce:
  1. create instance, wait until it becomes active.
  2. shelve the instance 
  $ nova shelve <instance_id or instance_name>

  3. A snapshot is created and uploaded to glance.
  4. Delete the snapshot and the image from which instance is created in the 1st step. (using admin credentials)
  5. unshelve the instance
  $ nova unshelve <instance_id or instance_name>

  6. Stack trace is printed on screen logs:

  nova-copute log:
     ImageNotFound: Image 442ea9bb-b664-41b4-b38b-8f5a690998d6 could not be found.

  glance-api log:
     2014-10-10 04:02:49.007 4546 DEBUG glance.api.v1.controller [-] Image 476b81bc-d1b1-40db-bad8-4f37ae3c66ac is not active 
  get_active_image_meta_or_404 /opt/stack/glance/glance/api/v1/controller.py:61
     2014-10-10 04:02:49.008 4546 INFO glance.wsgi.server [-] 10.69.4.130 - - [10/Oct/2014 04:02:49]
  "GET /v1/images/476b81bc-d1b1-40db-bad8-4f37ae3c66ac HTTP/1.1" 404 400 0.121644

  7. Once again unshelve the same instance.
  $ nova unshelve <instance_id or instance_name>

  8. This time you can not see the stack trace and instance goes in the active state successfully.
  9. When I use nova show command, it shows that instance is booted from the same image which is used in step #1.

  I have tested this scenario in the single node deployment.

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


Follow ups

References