euca-deregister deletes wrong image
Bug #744519 reported by
Tushar Patil
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
John Tran |
Bug Description
Steps to reproduce:-
1) Create ramdisk, kernel, machine images using glance upload.
2) $euca-describe-
IMAGE aki-00000002 (ipv6-kernel) private kernel
IMAGE ari-00000001 (ipv6-ramdisk) private ramdisk
IMAGE ami-00000003 (ipv6-disk-image) private machine aki-00000002 ari-00000001
3) Now try to deregister the ramdisk image using euca-deregister
$euca-degister ami-000001
Here I am trying to delete the machine image with id 1 which doesn't exists. So I was expecting euca-deregister should give me some error message. But in this case it actually deletes the ramdisk image ari-00000001.
Related branches
lp:~jtran/nova/lp744519
- Devin Carlen (community): Approve
- Vish Ishaya (community): Approve
- Brian Waldon (community): Approve
-
Diff: 111 lines (+28/-8)2 files modifiednova/api/ec2/cloud.py (+5/-1)
nova/tests/test_cloud.py (+23/-7)
summary: |
- euca-degister - deletes wrong image (for GlanceImageService) + euca-deregister - deletes wrong image (for GlanceImageService) |
Changed in nova: | |
assignee: | nobody → John Tran (jtran) |
Changed in nova: | |
status: | Triaged → Fix Committed |
Changed in nova: | |
milestone: | none → diablo-3 |
Changed in nova: | |
milestone: | diablo-3 → 2011.3 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Tested on nova revision 897 and glance revision 96.