Created attachment 1242514 [details]
Description of problem:
Engine re-assign MAC addresses without requesting to re-assign them on VM import from data domain.
When importing VM with MAC address that is out of range and we don't request to re-assign it, the VM get new MAC from the destination pool.
In the event ui log it reports -
' VM NEW2 has MAC address(es) 00:00:00:00:00:21, which is/are out of its MAC pool definitions'
But get new MAC instead.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Import VM from data domain with MAC address that is out of the range and don't request to re-assign it.
vNIC got new MAC
vNIC should remain with the original MAC address.
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Danken, this is marked as blocker for 4.1.0 after we released 4.1.0 RC, been in 4.1.1 target in the past 4 days.
Has this issue any workaround? Otherwise we need to plan a 4.1.0 respin and probably postpone GA.
If it missed the rebuild, then it should go to 4.1.1.
This is NOT an RC blocker, and it should not postpone GA. But I would like it to be included in the 4.1.0 d/s beta build scheduled for next week.
Verified on - 220.127.116.11-0.1.el7