NSXv3: security-group rule creation does not fail on duplicate rules

Bug #1563790 reported by Roey Chen
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Roey Chen

Bug Description

Creation of a security-group rule for a specific security-group should fail if an exact rule already exists for that security-group,
however, recent changes in security-groups made that this flow is valid and duplicated rules will be created successfully.

Roey Chen (roeyc)
Changed in vmware-nsx:
assignee: nobody → Roey Chen (roeyc)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to vmware-nsx (master)

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

Changed in vmware-nsx:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to vmware-nsx (master)

Reviewed: https://review.openstack.org/299299
Committed: https://git.openstack.org/cgit/openstack/vmware-nsx/commit/?id=c94678413423f6755dbabe9a7febe458408fb937
Submitter: Jenkins
Branch: master

commit c94678413423f6755dbabe9a7febe458408fb937
Author: Roey Chen <email address hidden>
Date: Wed Mar 30 03:53:17 2016 -0700

    Remove attribute not specified before checking duplicate sg rules

    The security-group extension secgroup-local-ip-prefix allows the user to
    specify a new rule attribute in the request, before passing the request
    to Neutron, we must remove ATTR_NOT_SPECIFIED if the attribute was not
    specified and replace it with None.
    The bug is due to change: I2bd6b3381c715c1286dfa10bf3b143c73fecf49d

    Closes-Bug: #1563790
    Change-Id: Ie921f9e41fc6b45d521bf8f9f041c773cdd19c31

Changed in vmware-nsx:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers