[Openstack-security] [Bug 1289195] Re: Duplicate security group name cause fail to start instance
Lee Li
lilinguo8212 at gmail.com
Tue Apr 1 03:18:58 UTC 2014
** No longer affects: neutron
--
You received this bug notification because you are a member of OpenStack
Security Group, which is subscribed to OpenStack.
https://bugs.launchpad.net/bugs/1289195
Title:
Duplicate security group name cause fail to start instance
Status in OpenStack Compute (Nova):
In Progress
Bug description:
When create a security group, the duplicate name is allowed.
In create a instance, duplicate sg name will cause exception and the instance will be started fail. So the duplicate name of sg should be not allowed.
In nova.network.neutronv2.API:allocate_for_instance
for security_group in security_groups:
name_match = None
uuid_match = None
for user_security_group in user_security_groups:
if user_security_group['name'] == security_group: # if have duplicate sg name, the name_match will not be None for the second matching.
if name_match:
raise exception.NoUniqueMatch(
_("Multiple security groups found matching"
" '%s'. Use an ID to be more specific.") %
security_group)
name_match = user_security_group['id']
if user_security_group['id'] == security_group:
uuid_match = user_security_group['id']
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1289195/+subscriptions
More information about the Openstack-security
mailing list