Bug 1612883

Created attachment 1473604 [details]
logs and screenshot

Description of problem:
As per our email conversation: virt-v2v copies the source VM vNIC MAC address on the target VM to prevent issues with software that relies on MAC address as an ID. To support this requirement, RHV should be configured to allow MAC addresses of migrated VMs using custom MAC pool range(s), otherwise virt-v2v will fail with the following error message:

v2v-import-20180806T084556-42111.log:ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Cannot import Virtual Machine, because that action would create duplicates in target MAC pool, which are not allowed. Either allow duplicate MACs in MAC Pool, or allow reassignment of bad MACs during import. Problematic NICs are  VmNetworkInterface:{id='cb317d58-da13-41ac-ba04-e2345d6656de', name='eth0', networkName='ovirtmgmt', vnicProfileName='null', vnicProfileId='null', speed='10000', type='3', macAddress='00:50:56:a4:9d:9a', active='true', linked='true', portMirroring='false', vmId='f0f2f50a-fb09-4973-a4e6-06de096cab9d', vmName='null', vmTemplateId='null', QoSName='null', remoteNetworkName='ovirtmgmt'}]". HTTP response code is 409.
resulting in CFME migration plan failure.

And RHV will fail with the following event on the VM:
<VM_NAME> has MAC address(es) <MAC_ADDRESS>, which is/are out of its MAC pool definitions.

Version-Release number of selected component (if applicable):
RHV 4.2.5.2-0.1.el7ev
CFME 5.9.4.2.20180802030318_f91df08

How reproducible:
100%

Steps to Reproduce:
1. Run migration plan on CFME to migrate a VM with vNIC that has MAC address which is not configured in the MAC pool of a target cluster on RHV.

Actual results:
Error message.

Expected results:
RHV MAC pool range should be configured accordantly. 

Additional info:
Similar bug opened last year:
https://bugzilla.redhat.com/show_bug.cgi?id=1467846#c4