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

Bug 1540877

Summary: OVA import name is not renamed.
Product: [oVirt] ovirt-engine Reporter: Nisim Simsolo <nsimsolo>
Component: BLL.VirtAssignee: Sharon Gratch <sgratch>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.1.4CC: bugs, mtessun, nsimsolo
Target Milestone: ovirt-4.2.2Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-06 09:37:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1049604    
Attachments:
Description Flags
engine.log, import started at 2018-02-01 11:12:08,260+02
none
vdsm.log
none
/vdsm/import.log none

Description Nisim Simsolo 2018-02-01 09:10:31 UTC 
Description of problem:
After renaming OVA name in import dialog and importing this OVA, the original OVA name is set on the VM instead of the renamed value that was set in import dialog.

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.1.5-0.0.master.20180130145919.gitd758f0f.el7.centos
vdsm-4.20.17-18.git4085e55.el7.centos.x86_64
qemu-kvm-common-ev-2.9.0-16.el7_4.13.1.x86_64
libvirt-client-3.2.0-14.el7_4.7.x86_64
sanlock-3.5.0-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Browse Webadmin -> Compute -> Virtual machines -> more options -> import, select virtual appliance (OVA) as source, set path, click load and continue to next import dialog.
2. Rename OVA name and start import.
3.

Actual results:
VM name is not renamed

Expected results:
Imported VM name from OVA should be renamed as set in the import dialog.

Additional info:
engine.log and vdsm.log attached
Comment 1 Nisim Simsolo 2018-02-01 09:18:17 UTC 
Created attachment 1389411 [details]
engine.log, import started at 2018-02-01 11:12:08,260+02
Comment 2 Nisim Simsolo 2018-02-01 09:21:10 UTC 
Created attachment 1389412 [details]
vdsm.log
Comment 3 Nisim Simsolo 2018-02-01 09:22:32 UTC 
Created attachment 1389413 [details]
/vdsm/import.log
Comment 4 Michal Skrivanek 2018-02-02 06:14:29 UTC 
related to bug 1529248?
Comment 5 Sharon Gratch 2018-03-06 09:37:44 UTC 

*** This bug has been marked as a duplicate of bug 1529248 ***