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

Bug 877737

Summary:	Import Vm without Disks Does not Import Vm Network Interfaces Properly
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Muli Salem <msalem>
Component:	ovirt-engine	Assignee:	Eli Mesika <emesika>
Status:	CLOSED WONTFIX	QA Contact:	Meni Yakove <myakove>
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.1.0	CC:	chetan, dyasny, edolinin, iheim, jbelka, lpeer, mavital, Rhev-m-bugs, sgrinber, yeylon, ykaul
Target Milestone:	---
Target Release:	3.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:		Doc Type:	Release Note
Doc Text:	Importing diskless virtual machines or templates will fail, or be imported without peripheral device such as network devices. To work around this issue, redefine diskless virtual machines or templates in the destination. Do not use the export and import process.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-21 09:52:44 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:

Description Muli Salem 2012-11-18 12:24:21 UTC

Description of problem:
When importing a Vm that does not have disks, the Vm Network Interfaces are added to the relevant table, but the Vm Device is not added, therefore the Vm Network Interfaces are not imported properly.


Version-Release number of selected component (if applicable):
si24.2

How reproducible:
Always.


Steps to Reproduce:
1. Create Vm
2. Add Vm interface
3. Export Vm
4. Remove Vm from Vms
5. Import Vm
  
Actual results:
The Vm Network Interfaces subtab is empty.


Expected results:
Vm Network Interfaces should be imported.


Additional info:

Comment 4 Simon Grinberg 2013-02-18 13:41:17 UTC

*** Bug 908691 has been marked as a duplicate of this bug. ***

Comment 5 Simon Grinberg 2013-02-21 09:46:03 UTC

*** Bug 906797 has been marked as a duplicate of this bug. ***