Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 870109

Summary: When import VM with custom MTU or VLAN network to DC that has those networks, the imported VM is created without the networks.
Product: Red Hat Enterprise Virtualization Manager Reporter: Meni Yakove <myakove>
Component: ovirt-engineAssignee: Moti Asayag <masayag>
Status: CLOSED NOTABUG QA Contact: Meni Yakove <myakove>
Severity: high Docs Contact:
Priority: high    
Version: 3.1.0CC: dyasny, iheim, lpeer, Rhev-m-bugs, sgrinber, yeylon, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-28 11:28:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine.log none

Description Meni Yakove 2012-10-25 14:54:21 UTC
Created attachment 633398 [details]
engine.log

Description of problem:
I have VM with four networks:
1. MTU 5000 (VM net)
2. VLAN 10 (VM net)
3. rhevm (VM net)
4. VLAN 30 MTU 7000 (VM net)

I exported the VM to export domain.
Importing the VM to another DC that have all the networks, after the VM imported I have only two networks on the new VM:
3. rhevm (VM net)
4. VLAN 30 MTU 7000 (VM net)





Version-Release number of selected component (if applicable):
rhevm-3.1.0-21.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1.Create 4 network and attach them to the host:
 MTU 5000 (VM net)
 VLAN 10 (VM net)
 rhevm (VM net)
 VLAN 30 MTU 7000 (VM net)
2.Create VM and add 4 nics to the VM using the network that created on step 1.
3.Attach export domain and export theVM.
4.Create new DC and create the same networks from step 1.
5.Detach the export domain from the old DC and attach it to the new DC.
6.Import the VM.
  
Actual results:
Only 2 networks was imported
rhevm (VM net)
VLAN 30 MTU 7000 (VM net)

Expected results:
All 4 networks should be imported.

Additional info:
From events tab:

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

Comment 1 Moti Asayag 2012-10-28 11:28:40 UTC
Taking a deeper look at the network names reveals the reason for leaving network names empty:

At the origin VM/template VM Data Center, the network names are: mtu_5000 and vlan_10.

At the destination Data Center, the names of a similar but not the same networks are: mtu5000 and vlan10 (no underscore).

The other two networks were called the same on both DCs: rhevm and vlan30_mtu7000.

The audit log in case of the failure was exact.

Attempt to import the VMs to the same DC worked fine.