[NEUTRON-6] creation of already existing resources could return 409 (Conflict) Created: 10/Sep/14  Updated: 19/Oct/17  Resolved: 19/Feb/15

Status: Resolved
Project: neutron
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Cédric Ollivier Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: PC

External issue ID: 1785

 Description   

Resource (network, subnet or port) creation returns 400 HTTP status (bad request) if its UUID already exists. It could be 409 (conflict) instead of 400 as written in neutron northbounds.

To reproduce it: create again an already existing resource(network, subnet or port).

 Comments   
Comment by Naresh kumar [ 06/Nov/14 ]

Olliver,
Can you please provide me the rest api you used for resource creation ?

Comment by Cédric Ollivier [ 12/Nov/14 ]

Neutron NB interfaces as called by the ODL Mechanism driver:

  • /controller/nb/v2/neutron/networks
  • /controller/nb/v2/neutron/subnets
  • /controller/nb/v2/neutron/ports
Comment by Bhavesh Kumar [ 28/Nov/14 ]

Made changes in the networkconfig.neutron.northbound api to return 409 Conflict exception on creating networks, subnets or ports with existing id.

Earlier it was returning 400 Bad request error which I changed to 409 Conflict exception.

https://git.opendaylight.org/gerrit/13183

Comment by Ryan Moats [ 17/Feb/15 ]

Moving from current project to neutron

Comment by Ryan Moats [ 19/Feb/15 ]

This is making requests to change the semantics of the neutron interface that are not in accordance with published documentation. Therefore rejecting as invalid.

Generated at Wed Feb 07 20:25:18 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.