yahoo-eng-team team mailing list archive

[Tzach Shefi <tshefi@xxxxxxxxxx>]

Public bug reported:

Description of problem: Deleting a none existing image should always
return same output.

Version-Release number of selected component (if applicable):
RHEL7
openstack-glance-2014.1-4.el7ost.noarch
python-glanceclient-0.12.0-1.el7ost.noarch
python-glance-2014.1-4.el7ost.noarch

How reproducible:
Every time

Steps to Reproduce:
1.  Upload a test image glance image-create ... 
2.  Glance image-list note new image's ID
3.  Delete that same image glance image-delete <imageID>
3.  Note output -> 
Request returned failure status. 
404 not found 
Image 07169a6f-bbce-4879-97d9-904fd69bb174 not found. 
    (HTTP 404): Unable to delete image 07169a6f-bbce-4879-97d9-904fd69bb174  

4. Now delete a none existing image glance image-delete <fakeImageID>
5. Output ->  
Request returned failure status. 
No image with a name or ID of '07169a6f-bbce-4879-97d9-904fd69bb179' exists. 

Actual results:
See step 3 /  5 each one returns another output

Expected results:
It would be better if both deletions would return same output. Preferably this one -> No image with a name or ID of '....' exists. 

>From a user's stand point deleting a none existing image should always
return same output, the fact that one of the images still has a DB
listing which causes a different output is a bit misleading for someone
not familiar with system's inner workings.  If this unique output is a
must maybe improve wording, "No image with name of ID....   exists, but
there is an old listing in DB for it.. "

** Affects: glance
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1333119

Title:
  Glance image delete output

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  Description of problem: Deleting a none existing image should always
  return same output.

  Version-Release number of selected component (if applicable):
  RHEL7
  openstack-glance-2014.1-4.el7ost.noarch
  python-glanceclient-0.12.0-1.el7ost.noarch
  python-glance-2014.1-4.el7ost.noarch

  How reproducible:
  Every time

  Steps to Reproduce:
  1.  Upload a test image glance image-create ... 
  2.  Glance image-list note new image's ID
  3.  Delete that same image glance image-delete <imageID>
  3.  Note output -> 
  Request returned failure status. 
  404 not found 
  Image 07169a6f-bbce-4879-97d9-904fd69bb174 not found. 
      (HTTP 404): Unable to delete image 07169a6f-bbce-4879-97d9-904fd69bb174  

  4. Now delete a none existing image glance image-delete <fakeImageID>
  5. Output ->  
  Request returned failure status. 
  No image with a name or ID of '07169a6f-bbce-4879-97d9-904fd69bb179' exists. 

  Actual results:
  See step 3 /  5 each one returns another output

  Expected results:
  It would be better if both deletions would return same output. Preferably this one -> No image with a name or ID of '....' exists. 

  From a user's stand point deleting a none existing image should always
  return same output, the fact that one of the images still has a DB
  listing which causes a different output is a bit misleading for
  someone not familiar with system's inner workings.  If this unique
  output is a must maybe improve wording, "No image with name of ID....
  exists, but there is an old listing in DB for it.. "

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