Bug 1004386

Description of problem:
When trying to to import a VM into a DC that doesn't have a VNIC profile for one of the networks that the VM is connected to an old warning that doesn't take VNIC profiles into account is shown.


Version-Release number of selected component (if applicable):
3.3.0-0.19.master.el6ev


How reproducible:
100%

Steps to Reproduce:
1. On one DC create a VM that has a VNIC profile for network sw1 on nic1 and export the VM.
2. Prepare a second DC that has network sw1 but delete all the VNIC profiles for that network. 
3. Import the VM to the second DC.

Actual results:
The following warning is shown:

"While importing VM <UNKNOWN>, the Network/s sw1 were found to be Non-VM Networks or do not exist in Cluster. Network Name was not set in the Interface/s nic1."

The VM is imported but no profile is selected for nic1.


Expected results:
The message should contain the VM name instead of "<UNKNOWN>" and it should say something similar to "no matching VM interface profile was found for sw1".

Additional info:
Probably as a result of the fix to https://bugzilla.redhat.com/show_bug.cgi?id=1001068 this scenario can also be trigged if we change step 2 above to the following:

2. On the second DC all the VNIC profiles for sw1 should have port mirroring enabled (which makes them unusable for imported VM).


Perhaps not allowing deletion or modificatoion of the default profiles will block this and other similar scenarios.