booting vms via --nic port-id=<> regression

[Aaron Rosen]

nova boot --nic port-id=<.> doesn't seem to work anymore. It looks like this might be the commit that broke it: 394c693e

[Aaron Rosen (arosen)]

What I mean by doesn't work is that if you do:
nova boot --image cirros-0.3.1-x86_64-uec --flavor 1 --nic port-id=a2183706-63c0-4468-8194-8fe4ce064558 vm1

when you login to that vm there is no eth0 interface only the loop back. If you look at the running kvm process it dosen't have
the -netdev tap option running with the process either.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/25563
Committed: http://github.com/openstack/nova/commit/57689f26f37fe3de33a666a2d7d0731eae9c7ea9
Submitter: Jenkins
Branch: master

commit 57689f26f37fe3de33a666a2d7d0731eae9c7ea9
Author: Dan Smith <email address hidden>
Date: Wed Mar 27 14:45:06 2013 -0700

    Fix quantum nic allocation when only portid is specified

    A simple omission at the end of allocate_for_instance() was preventing
    the function from returning information about the newly-allocated port
    if one was not actually allocated from a network (i.e. if it was
    provided as input). This fixes that and adds a test which would have
    caught it.

    Fixes bug 1160560

    Change-Id: Ib0d7d91acfe5bd684cdfc072fe47c8115c2f91b3

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: milestone-proposed
Review: https://review.openstack.org/25615

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/25615
Committed: http://github.com/openstack/nova/commit/5b0917a3eea418c883561414c5491ffdedab9428
Submitter: Jenkins
Branch: milestone-proposed

commit 5b0917a3eea418c883561414c5491ffdedab9428
Author: Dan Smith <email address hidden>
Date: Wed Mar 27 14:45:06 2013 -0700

    Fix quantum nic allocation when only portid is specified

    A simple omission at the end of allocate_for_instance() was preventing
    the function from returning information about the newly-allocated port
    if one was not actually allocated from a network (i.e. if it was
    provided as input). This fixes that and adds a test which would have
    caught it.

    Fixes bug 1160560

    (cherry-picked from 57689f26f37fe3de33a666a2d7d0731eae9c7ea9)

    Change-Id: Ib0d7d91acfe5bd684cdfc072fe47c8115c2f91b3