Description of problem: On a setup where the MAC address pool has been used up, trying to import a VM results in a generic failure message. The message doesn't mention the fact that there are not enough MAC addresses. Version-Release number of selected component (if applicable): 3.3.0-0.19.master.el6ev How reproducible: 100% Steps to Reproduce: 1. Create NICs until the MAC address pool is depleted. 2. Try to import a VM. Actual results: The import appears to start but fails a few seconds with the following message in the log: "Failed to import Vm VM1_Copy to Data Center DC_33, Cluster cluster_33" Expected results: There should be a pop up error stating that there are "Not enough MAC addresses left in MAC Address Pool." (the wording that is used in similar cases) For new NICs on existing VMs, there is an option to specify a custom MAC address if there are not enough MAC addresses. It would be nice to allow entering a custom MAC address in this situation as well instead of blocking the import. Additional info:
Created attachment 797882 [details] engine log
This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step.