creating a net association twice results in a internal error

Bug #1512714 reported by Mathieu Rohon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-bgpvpn
Fix Released
Low
Mathieu Rohon

Bug Description

running the following command twice result in an internal server error after the second command :

#neutron bgpvpn-net-assoc-create --network 'net-id' 'bgpvpn-id'

The expected behavior would be not to create a new entry but return the existing one

Changed in bgpvpn:
importance: Undecided → Low
Changed in bgpvpn:
milestone: none → liberty
Changed in bgpvpn:
status: New → Confirmed
Changed in bgpvpn:
assignee: nobody → Mathieu Rohon (mathieu-rohon)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-bgpvpn (master)

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

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

Reviewed: https://review.openstack.org/252948
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=bd6471dbbc61fc30eac91d86b6908724179b48b3
Submitter: Jenkins
Branch: master

commit bd6471dbbc61fc30eac91d86b6908724179b48b3
Author: Mathieu Rohon <email address hidden>
Date: Thu Dec 3 13:19:18 2015 +0000

    Raise an exception for identical associations

    When a request asks for creating a network association that
    already exists, we have to catch the DB exception and raise an
    exception that respond an error code 400.

    Change-Id: Iafcaa6b016bc5f39f5ee1d64ef7ff627efa74183
    Closes-Bug: 1512714

Changed in bgpvpn:
status: In Progress → Fix Committed
Changed in bgpvpn:
status: Fix Committed → Fix Released
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.