Unable to launch instance when there are two security groups with same name in a tenant (with Neutron back-end)

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

Bug Description

When there are two security groups with same name, an error will be raised if one of the security group selected:

Error: Multiple security_group matches found for name 'test1', use an ID to be more specific. (HTTP 409) (Request-ID: req-0bd2a1e7-2c63-49ad-b64b-21b8e976df67)

(amotoki) This only occurs with Neutron networking back-end.

Tags: neutron
Liyingjun (liyingjun)
Changed in horizon:
assignee: nobody → Liyingjun (liyingjun)
Changed in horizon:
status: New → In Progress
Revision history for this message
Akihiro Motoki (amotoki) wrote :

Using a same name for multiple security groups is use-less when a user uses Horizon since the user cannot distinguish two security groups in Launch Instance form. Thus I set the priority to Low.

Changed in horizon:
milestone: none → liberty-3
importance: Undecided → Low
summary: Unable to launch instance when there are two security groups with same
- name
+ name in a tenant (with Neutron back-end)
description: updated
tags: added: neutron
Thierry Carrez (ttx)
Changed in horizon:
milestone: liberty-3 → liberty-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on horizon (master)

Change abandoned by Li Yingjun (<email address hidden>) on branch: master
Review: https://review.openstack.org/212279

Revision history for this message
Liyingjun (liyingjun) wrote :
Changed in horizon:
status: In Progress → Fix Released
Thierry Carrez (ttx)
Changed in horizon:
milestone: liberty-rc1 → 8.0.0
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.