reason should be shown when failing to delete a security group

[Tanja Roth]

If you are trying to delete a security group that is assigned to an instance that is running, the security group cannot be deleted. The Dashboard only gives a generic message that the group cannot be deleted without mentioning why.
Instead of letting the user search for the reason, a specific message would be much better:

"Security Group <xyz> is still assigned to instances <abc>. You need to do <cde> before you can delete the group."

--

[amotoki]
The current consensus looks like adding a message like "Security group is still in use" on the UI. This can be done by checking the exception from openstack_dashboard.api.neutron (and neutronclient.common.exceptions). 409 means the requested security group is in use.

[Ashok kumaran B (ashokkumaran-b)]

Hi

Security group can be modified on the fly when the instance is running. You can either remove an old security group or add a new security group. That's pretty much possible.
if you are running grizzly you might wanna take this patch https://review.openstack.org/#/c/32679(or else you need to wait for 2013.1.3 patch release) which can solve the problem. I believe horizon got nothing much to do here.

[Verónica Musso (veronica-a-musso)]

When user tries to delete an assigned security group, the Nova function in charge of destroying it, throws an exception with the message: "Security group is still in use" (see destroy function in nova/nova/compute/api.py). Also, the code is prepared to manage its translations.
We could add that message to the current one ("Unable to delete: group_name") when the exception is caught and the UI message is printed. The only thing to consider is that the method is general and it manages several exceptions, then we would print all the exception messages (see handle function in horizon/horizon/tables/actions.py). Is that ok?

[Tanja Roth (taroth)]

IMHO, a message like "Security group is still in use" on the UI would be fine.
I'm not very deeply into the code, therefore I cannot assess if printing all the exception messages on the UI could turn into a problem - I leave that that for others to judge. To me, Veronica's proposal sounds good.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/62026

[Masco (masco)]

removing the assignee since no activity for long time

[surbhi sarda (surbhisarda)]

can i work on this bug?

[Jyothi Saroja (saroja-daggu)]

Yes, you can.
-----<email address hidden> wrote: -----
To: <email address hidden>
From: surbhi sarda <email address hidden>
Sent by: <email address hidden>
Date: 09/16/2016 11:47AM
Subject: [Bug 1210540] Re: Usability: Deleting a Security Group

can i work on this bug?

--
You received this bug notification because you are a bug assignee.
https://bugs.launchpad.net/bugs/1210540

Title:
  Usability: Deleting a Security Group

Status in OpenStack Dashboard (Horizon):
  Confirmed

Bug description:
  If you are trying to delete a security group that is assigned to an instance that is running, the security group cannot be deleted. The Dashboard only gives a generic message that the group cannot be deleted without mentioning why.
  Instead of letting the user search for the reason, a specific message would be much better:

  "Security Group <xyz> is still assigned to instances <abc>. You need
  to do <cde> before you can delete the group."

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1210540/+subscriptions
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you