Getting 500 While booting VM through router interface using same port id

[Pavan Gunjal]

1 . Component : Router
2. OS:- Local devstack machine
3. Priority -> Major

Test steps:
 1.create a network (quantum net-create <name>)
 2.create a subnet (quantum subnet-create <network> <cidr>)
 3.create port (quantum port-create <network_id>)
 4.create router( quantum router-create <name>)
 5.add router interface using same port_id
 6.boot vm (nova boot --nic port-id=<port_id>(port_id same as in step above))

Expected Result :
we should probably handle this more gracefully and raise a better error message.(e.g.400,404)

Actual result :
500 error code seen while booting vm using same port_id which is in-use.

[Mark McClain (markmcclain)]

There's nothing that impacts Quantum/OpenStack security. Mind if I make this bug public?

[Salvatore Orlando (salvatore-orlando)]

I think this is a Nova bug.
No exception is raised in Quantum at all.
Nova raises a port in use since device_id!=None, and this port in use error should be converted into a 409 Conflict IMHO.

[Salvatore Orlando (salvatore-orlando)]

Feel free to revert project assignment if you think this is a Quantum bug.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/34997
Committed: http://github.com/openstack/nova/commit/48b31c9a1f5d2a45d881e70c6223411c5abbcb72
Submitter: Jenkins
Branch: master

commit 48b31c9a1f5d2a45d881e70c6223411c5abbcb72
Author: Rohit Karajgi <email address hidden>
Date: Sat Jun 29 06:31:31 2013 -0700

    Fix HTTP response for PortInUse during boot

    If an in use port is passed as a network parameter in the request, Nova API
    should raise an HTTPConflict (409) error

    Fixes bug #1160887

    Change-Id: I60103610f9143f1c668927fe40d10a14b39b4c25