Previously, when importing a virtual machine from a data storage domain, if the virtual machine had a “bad” MAC address, a MAC collision may have occurred in the target LAN. A “bad” MAC address is an address that is already in use or an address that is out of the range in the target cluster. In this release, it is possible to assign a new MAC address when importing the virtual machine from a data storage domain.
See bug https://bugzilla.redhat.com/show_bug.cgi?id=1226206
Update section: https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide/#sect-Importing_Existing_Storage_Domains
Assigning to Emma for review.
Yvgeny, I have a few question regarding the feature that you developed>
1. Please let me know exactly what appears in the UI if an imported VM uses the same mac address as an existing vm, or an address that is not in the range.
Does an event appear at the bottom of the screen? An icon in the window, a message? this is not clear in the original bug.
A screenshot would be great.
2. Is there a feature page?
3. How does the user enter a new mac address? Again, a screenshot would help.
Created attachment 1256930 [details]
MAC in use example
1. Please find the attached screenshot. You can see there an exclamation mark next to the VM row and the tooltip that describes why the exclamation mark appeared.
3. A user doesn't enter the MAC address, but request allocation of a new MAC for the "bad" addresses on the VM that is being imported. On the screenshot, you can see the new column "Reassign bad MACs" that is used for that.
The final draft was approved offline by Yevgeny.
Tahlia, please review this merge request:
*** Bug 1421009 has been marked as a duplicate of this bug. ***
The updated Administration Guide can now be viewed in the customer portal. Section 8.6.5. Importing Virtual Machines from Imported Data Storage Domains.