Hide Forgot
Description of problem: Adding 10 nics to a VM makes ovirt presenting them to VMs in alphabetical order. (ie nic1, nic10, nic2, nic3, etc) So on the VM, nic2 actually becomes nic3. Version-Release number of selected component (if applicable): How reproducible: Easy Steps to Reproduce: 1. Add 10 nics to vm 2. Connect nic2 to networkA on ovirt 3. Configure networkA on the VM on nic3 4. Observe network connectivity on nic3 5. Configure networkA on the Vm on nic2 6. Network connectivity fails Actual results: Shouldn't work on nic3 on the VM, and should work with nic2 Expected results: Connectivity should be available on nic2 Additional info:
Actual version is 3.6.3.4, it's just not showing in the dropdown..
May I ask whether you have a real use case for 10 vnics? Can you elaborate on it?
My firewall team said that they have license for 10 interfaces and they don't want to reboot the firewalls for every addition, so let's just provision all of them at once. I realize it's an edge case, also for now they're ok with 9nics, so I'm good if you deem this not worthy to fix.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
oVirt allocates mac addresses to vNICs based on their alphanumeric order (ReorderVmNicsCommand.java). I think that you can work around this surprising sort by manually editing the nic names (nic1->nic01 etc) when you add the vNICs. Would you try that out? (I am a bit reluctant to add a more complex heuristic for sorting vnics, such as one were if all vnics has nic<number> names they are sorted based on <number>)
The proposed/implemented solution is sorting vNics in ReorderVmNicsCommand by the natural order. The command could be activated by one of the following flows: * UI - Add all vNics in the create VM dialog, after VM is created UI doesn't expose an interface to the command, so a subsequent vNic manipulation would not be covered by the change * REST API - vnics re-order could be activated at any stage prior the VM activation
Verified on - 4.1.0.1-0.1.el7