The typical use case of importing a VM from from VmWare is that of relocation, not clone. The original VM is stopped, and the workload is expected to run on oVirt with as little interruption as possible. Thus, v2v import should allow keeping the original MAC. Kaul suggests that this should be the only option. If the MAC is "bad" in any way, the NIC can be imported as "unplugged", and the user can request to reassign it in a follow-up call. Note that this means that Bug 1437152 was not a bug, but a feature, which we would like to reintroduce.
https://gerrit.ovirt.org/#/c/89082/ is changing behavior just for the importVmFromConfiguration using OVF, not affecting the current integrated v2v.
As mentioned in comment 1, the current integrated v2v is not affected by this change.
Verified on: ovirt-engine-4.2.2.5-0.1.el7.noarch vdsm-4.20.23-1.el7ev.x86_64 virt-v2v-1.36.10-6.el7.x86_64 Steps of verification: 1. Create a VM on VMWare with NIC and MAC address. 2. Import the VM from RHEV via V2V. Results: The VM was imported with the NIC plugged and up. The MAC address remained to the one in VMWare.
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.