vCenter VM can have different NIC MAC than requested
|Assignee:||Sergio Semedi||% Done:|
|Target version:||Release 5.4.3|
|Affected Versions:||OpenNebula 5.4|
It can happen, maybe due to the MAC address collision detection in the vCenter, that VM assigned NIC MAC address is different, then requested.
Example: Have VNET w/ IPv4 AR containing IP 10.0.1.236 (MAC 02:00:0a:00:01:ec). If VM is deployed with this NIC MAC/IP, some superior power can decide there is a problem to assign this particular MAC address and chooses different one. In my case 00:50:56:a3:dd:bd. This wrong MAC can be seen:
1. inside the VM
2. in the vCenter
but not in the OpenNebula, there is still the originally requested MAC/IP.
If I hot-attach NIC with problematic MAC/IP, it works correctly. Looks like the problem is only when used with newly deployed VM.
Also, there is problem with detaching such NIC, becase detach works with MAC addresses and in this situation, they are different in VM/vCenter and ONE. So, detach proceeds in the OpenNebula, but NIC is still attached.
Checked on the vOneCloud 3.0.2/ONE 5.4.1.