NIC ordering after a hard reboot
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
New
|
Undecided
|
Unassigned | ||
Bug Description
NIC ordering at boot time was addressed but there is still more NIC ordering problems
* using grizzly 2013.1.2
* using libvirt/KVM
* using quantum 2013.1.2 (with linuxbridge plugin)
* using config drive for network configuration
I boot VMs with 2 NICs (WAN and LAN)
I want WAN to be attached the first NIC in my VM
I want LAN to be attached the second NIC in my VM
to obtain this desired ordering, I pass the two networks in this order to "nova boot"
Because of a previous patch, this will work for the FIRST instantiation of the VM (the initial boot) but a hard reboot, or a resize/migration will result in a VM with crossed-over NICs depending on the network natural order (alphabetical order of the networks UUID)
If my WAN UUID is inferior (alphabetical order) to the LAN UUID, the boot, the hard reboot and the migrate/resize will work
If my LAN UUID is inferior to the WAN UUID, the boot will work but any other hard operations like "hard reboot" and resize will fail as the networks will be presented in their natural order to the newly (re-)created VM...
the NIC ordering passed to nova boot must remain enforced throughout the life of the VM, including heavy operations where libvirt/kvm recreates a VM from scratch.
Boris
