Comment 5 for bug 1400037

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/144882
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cd6c48abd592e3a40153c555ee2aa91ac773c820
Submitter: Jenkins
Branch: master

commit cd6c48abd592e3a40153c555ee2aa91ac773c820
Author: venkata anil <email address hidden>
Date: Sun Jan 4 13:42:19 2015 +0000

    boot instance with same net-id for multiple --nic

    'allow_duplicate_networks' flag should allow an instance to have
    multiple vNICs attached to the same Neutron network.

    After setting this flag to true, booting instance with multiple
    interfaces to attach to same network(with same net-id) like below
    is failing.

    nova boot --flavor m1.small --image rhel7-new
    --nic net-id=52fc18b6-397a-45d6-b8db-fb32accd00e5
    --nic net-id=52fc18b6-397a-45d6-b8db-fb32accd00e5 vm100

    We have check for duplicate networks at nova api layer(i.e nova/api/
    openstack/compute/servers.py). We can just skip this check when we are
    using neutron. Because we already have same check in network api(i.e
    nova/network/neutronv2/api.py) and also as 'allow_duplicate_networks'
    flag is only for nova neutron.

    Closes-Bug: #1400037
    Change-Id: I7ee4e03a8fda3796606fb4618b95999b7580561d