Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1199896

Summary: horizon is using the Security Group name rather than the ID
Product: Red Hat OpenStack Reporter: Eduard Barrera <ebarrera>
Component: python-django-horizonAssignee: Radomir Dopieralski <rdopiera>
Status: CLOSED EOL QA Contact: Ido Ovadia <iovadia>
Severity: medium Docs Contact:
Priority: high    
Version: 5.0 (RHEL 7)CC: aortega, athomas, berrange, dasmith, ebarrera, eglynn, kchamart, mchappel, mrunge, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1292851 1293232 (view as bug list) Environment:
Last Closed: 2017-06-30 13:29:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1292851, 1293232    

Description Eduard Barrera 2015-03-09 08:04:16 UTC
Description of problem:


I used a heat template to create  some test VMs, Networks and Security groups.

As a side effect I managed to create 2 security groups with the same name.

I tried launching a new VM using one of these security groups  (Project -> Compute -> Images -> "RHEL 6" -> Launch)

This resulted in an error "Error: Multiple security_group matches found for name 'SSH and ICMP', use an ID to be more specific. (HTTP 409) (Request-ID: req-c79e0aa9-a42e-469e-836d-8ed6e98d71ae)"

If I create the VM without associating the SecurityGroup, and then associate the SecurityGroup afterwards this works.

Creating a VM under the same conditions using Heat worked fine.

Based on https://bugs.launchpad.net/nova/+bug/1289195 horizon is using the Security Group name rather than the ID when creating a new Instance.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 12 Radomir Dopieralski 2015-08-24 14:52:40 UTC
I submitted a patch with a partial fix upstream at https://review.openstack.org/#/c/211046/2

Unfortunately, that only works for Neutron. With Nova-Network, more work is required to allow passing the security groups by ID in the API.

Comment 13 Radomir Dopieralski 2015-09-28 09:54:21 UTC
A patch for nova-network to accept group ids: https://review.openstack.org/#/c/211046/

Comment 14 Radomir Dopieralski 2015-10-01 14:16:47 UTC
The patch for kilo has been merged: https://review.openstack.org/#/c/229767/

Comment 15 Eoghan Glynn 2015-12-15 16:12:01 UTC
Nova patch on master https://review.openstack.org/217292

Comment 16 Radomir Dopieralski 2015-12-15 16:16:09 UTC
We have a fix for Neutron, that we can backport, however, the fix for Nova-Network is still being reviewed, and since it requires an API change, it's unlikely to be backported. Does the client use Neutron or Nova-Network?

Comment 17 Mark Chappell 2015-12-15 16:27:10 UTC
neutron

Comment 18 Radomir Dopieralski 2015-12-18 14:31:46 UTC
In that case the problem is already solved by the two patches, which are already merged upstream in horizon in liberty and kilo. We need to just backport them to our horizon 5.0.

Comment 19 Matthias Runge 2015-12-21 14:51:08 UTC
Backport to rhos-6 is https://bugzilla.redhat.com/show_bug.cgi?id=1293232

Comment 20 Scott Lewis 2017-06-30 13:29:58 UTC
Red Hat OpenStack Platform version 5 is now End-of-Life, and as such will not have further updates. See https://access.redhat.com/support/policy/updates/openstack/platform/ for full support lifecycle details.