Horizon can't delete volume stuck in creating state

Bug #1318649 reported by Tzach Shefi
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Invalid
Medium
Ankur

Bug Description

Description of problem:
If a volume is stuck in creating state, it can't be deleted from Horizon -> Error: You are not allowed to delete volume: 9fd9....

While deleting from CLI works fine
# cinder delete ... volume is deleted.

Added info about setup:
Semi distributed setup, via packstack, on rhel7 beta
Cinder's backend is a distributed Gluster volume.

Version-Release number of selected component (if applicable):
RHEL7
openstack-dashboard-2014.1-4.el7ost.noarch
openstack-cinder-2014.1-3.el7ost.noarch

How reproducible:
Everytime

Steps to Reproduce:
1. Don't recall how I managed to create volumes which got stuck in "creating" state.
2. Once you have such volumes try to delete them from Horizon volumes tab - fails with error notice.
3. Deleting same volumes from CLI works.

Actual results:
Volume isn't deleted getting: -> Error: You are not allowed to delete volume: 9fd94b49-e3a7-4b79-801e-a50c985b29f7

Expected results:
Volume should be deleted successfully

Additional info:
Related RFE about adding option from Horizon to force delete volume in error state.
https://blueprints.launchpad.net/horizon/+spec/force-delete-volumes

Tags: volume
Revision history for this message
Tzach Shefi (tshefi) wrote :
Revision history for this message
Julie Pichon (jpichon) wrote :

We have a limited number of states during which we allow deletion, it sounds like it would be worth revisiting.

https://github.com/openstack/horizon/blob/cacd93ea49/openstack_dashboard/dashboards/project/volumes/volumes/tables.py#L34

tags: added: volume
Changed in horizon:
importance: Undecided → Medium
lokesh s (lokesh-s)
Changed in horizon:
assignee: nobody → lokesh s (lokesh-s)
Revision history for this message
Lawrance (jing) wrote :

hi, i think we should allow deletion action while the volume is in creaing state, the cinder service sometimes is not normal, it will always be in creating state , really need to allow deletion action!!!

Changed in horizon:
status: New → Confirmed
Changed in horizon:
status: Confirmed → In Progress
Changed in horizon:
status: In Progress → New
assignee: lokesh s (lokesh-s) → nobody
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on horizon (master)

Change abandoned by Rob Cresswell (<email address hidden>) on branch: master
Review: https://review.openstack.org/134119
Reason: Patch abandoned due to inactivity.

Adriano (dritec)
Changed in horizon:
assignee: nobody → Adriano (dritec)
Adriano (dritec)
Changed in horizon:
assignee: Adriano (dritec) → nobody
Revision history for this message
Ankur (ankur-gupta-f) wrote :

Wouldn't this be solved by creating a "Reset State" action. Reset would just put the Volume in an error state (db entry). Which would then allow for deletion.

Ankur (ankur-gupta-f)
Changed in horizon:
assignee: nobody → Ankur (ankur-gupta-f)
Revision history for this message
Ankur (ankur-gupta-f) wrote :

Using "Update Volume Status" an admin can put the volume into an error state, from which it can be deleted

Changed in horizon:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.