Multiple security groups with same name can be created

[Unmesh Gurjar]

Branch: master

Steps to reproduce:
1. Create multiple security groups simultaneously, having the same name.
2. Observe the result for each.

Expected Behavior:
The first security group should be created and second must receive a HTTP 409 response with an appropriate message.

Actual Behavior:
Multiple security groups having same name get created.

[Boris Pavlovic (boris-42)]

We will be able to fix it only after bp/db-unique-keys will be implemented.

[Joe Gordon (jogo)]

Since fixing this will require a DB migration, lets hold fixing this until Havana, and this will be marked as a known issue in Grizzly.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/32886
Committed: http://github.com/openstack/nova/commit/231c97007c6290f22807c0d4a605d9d95d4eb3af
Submitter: Jenkins
Branch: master

commit 231c97007c6290f22807c0d4a605d9d95d4eb3af
Author: Roman Bogorodskiy <email address hidden>
Date: Thu Jun 13 07:41:51 2013 -0400

    Add unique constraint for security groups

    - Add unique constraint (project_id, name, deleted)
      for security_groups
    - Define new SecurityGroupExists exception
    - Drop security_group_exists() in favor of catching
      SecurityGroupExists exception for security_group_create()

    Fixes bug #1093458

    Blueprint: db-enforce-unique-keys

    Change-Id: Id9a1427587cc9250942d0abd9eafc69861352d9b