Description of problem: Adding nics to a VM with the same mac should be blocked. On GUI it is blocked. Version-Release number of selected component (if applicable): si29 Additional info: 1. On 3.2 REST blocks it. 2. This was discovered when the VM was rerun, and failed on: "XML error: Attempted double use of PCI Address '0:0:3.0'" in vdsm log.
Important addition: The mac of the 2nd nic added, is the same mac, but yet differ in case sensitivity! If the exact mac is given to the 2nd nic, including case sensitivity - the nic add fails (that this mac already exists...) For example if the mac is: 00:1a:4a:23:a0:db, adding a second nic with mac 00:1a:4a:23:a0:db will fail, but adding a 2nd nic with mac 00:1A:4A:23:A0:DB will succeed.
When the nic is added from the GUI, and the mac is the same, but it's case sensitivity is different, The GUI blocks adding this nick, claiming it's the same mac. If the fix for this bug should be on the network side, and the behaviour is expected to be the same from GUI and REST, then no need for the GUI block.
*** Bug 974116 has been marked as a duplicate of this bug. ***
verified on is14, adding MAC via REST is not key sensitive [RHEVM shell (connected)]# add nic --vm-identifier F19 --name nic4 --plugged True --linked True --mac-address "00:1a:4a:23:a0:db" id : 97479acd-14f0-4292-bdf3-51405abb3ecd name : nic4 active : True interface : virtio linked : True mac-address: 00:1a:4a:23:a0:db plugged : True vm-id : 19eac407-63aa-4745-b4df-03ddbdb46cda [RHEVM shell (connected)]# add nic --vm-identifier F19 --name nic5 --plugged True --linked True --mac-address "00:1A:4A:23:A0:DB" error: status: 409 reason: Conflict detail: MAC Address is already in use.
Closing - RHEV 3.3 Released