Bug 1540877 - OVA import name is not renamed.
Summary: OVA import name is not renamed.
Keywords:
Status: CLOSED DUPLICATE of bug 1529248
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.2.1.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.2.2
: ---
Assignee: Sharon Gratch
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks: 1049604
TreeView+ depends on / blocked
 
Reported: 2018-02-01 09:10 UTC by Nisim Simsolo
Modified: 2018-03-06 09:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-06 09:37:44 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
engine.log, import started at 2018-02-01 11:12:08,260+02 (2.24 MB, text/plain)
2018-02-01 09:18 UTC, Nisim Simsolo
no flags Details
vdsm.log (6.18 MB, text/plain)
2018-02-01 09:21 UTC, Nisim Simsolo
no flags Details
/vdsm/import.log (783.75 KB, text/plain)
2018-02-01 09:22 UTC, Nisim Simsolo
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.