Select All on Security Groups Can Cause The Delete Button to Get In a Weird State

Bug #1018158 reported by John Postlethwait
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Low
Unassigned

Bug Description

Repro:

1) Have ONLY one Security Group. (the group "default")
2) Go to Access and Security.
3) Click the "select all" checkbox at the top of the Security Group table.
4) The "default" group will be selected.
5) The "default" group cannot actually be deleted, so the "Delete Security Groups" button at the top of the table will stay disabled.
6) Click on the "Select all" checkbox again.

Expected:

The "Delete Security Groups" button will stay disabled, and the checkboxes will all be unchecked. Clicking on the "Delete Security Groups" button does nothing (as it is disabled.)

Actual:

The "Delete Security Groups" button is ENABLED when all of the checkboxes become unchecked. You can then click on it and get the prompt warning/asking you about deleting the Security Groups.

Also:

We probably want to NOT have the checkboxes for items that cannot be deleted, as selecting it, then not being able to delete the one you have selected is confusing, since we offer no explanation as to why you cannot delete the default security group.

Devin Carlen (devcamcar)
Changed in horizon:
status: New → Confirmed
importance: Undecided → Low
milestone: none → folsom-3
assignee: nobody → Nebula (nebula)
Revision history for this message
Gabriel Hurley (gabriel-hurley) wrote :

This appears to have been fixed. Checking it now simply allows it to be selected. I don't really see a problem with allowing it to be selected. If you try to delete it you receive a very informative error.

Changed in horizon:
status: Confirmed → Fix Committed
Thierry Carrez (ttx)
Changed in horizon:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in horizon:
milestone: folsom-3 → 2012.2
Curtis Hovey (sinzui)
Changed in horizon:
assignee: Registry Administrators (registry) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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