My fault, one just pointed me out that we actually try to preserve NIC ordering when calling Neutron :
https://github.com/openstack/nova/blob/286cb904055eec3525fb61b2a0f93b14448bdd3e/nova/network/neutronv2/api.py#L2522 Looks to me like a legit bug by the fact that when the user provides a port instead of a network ID, we don't preserve the ordering since ports are treated separatly from the above. https://github.com/openstack/nova/blob/286cb904055eec3525fb61b2a0f93b14448bdd3e/nova/network/neutronv2/api.py#L841-L848 ** Changed in: nova Status: Invalid => Confirmed ** Changed in: nova Importance: Wishlist => Low ** Tags added: neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1696664 Title: Order of the interfaces is not honored when using virt and SR-IOV interfaces Status in OpenStack Compute (nova): Confirmed Bug description: When launching an instance using the following: # nova boot --flavor m1.small --image <image id> --nic net-id=<net id> --nic port-id=<port id> vm1 Where the first interface is a non SR-IOV port and the second one is SR-IOV port the order is not preserved ,i.e. The first interface of the instance is the SR-IOV port. Version: openstack-nova-compute-15.0.3-3.el7ost.noarch To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1696664/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
