Bug 1807929 - importing VM uses the old (original) name instead of the new one
Summary: importing VM uses the old (original) name instead of the new one
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.4.0
: ---
Assignee: shani
QA Contact: Daniel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-27 14:03 UTC by shani
Modified: 2020-05-20 20:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-20 20:03:13 UTC
oVirt Team: Storage
Embargoed:
pm-rhel: ovirt-4.4+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 107403 0 master MERGED core, webadmin: use the supplied name on VM registration 2020-04-12 07:05:40 UTC

Description shani 2020-02-27 14:03:05 UTC 
Description of problem:
When importing a VM from a data storage domain on the UI, and changing its name, the import process ignores the new name entered, and trying to import the VM with its original name. 

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.0_master-git50e0ffb3648

How reproducible:
100%

Steps to Reproduce:
1. Have an SD with a VM (or more) on it.
2. Detach that SD (maintenance > detach). 
3. Attach that SD back (now you should have a 'VM import' tab on that SD).
4. Choose the VM and change its name.

Actual results:
The imported VM was created with the original name.

Expected results:
The imported VM should be called by the new name specified.

Additional info:
-
Comment 1 Ilan Zuckerman 2020-04-05 14:21:36 UTC 
verified on 4.4.0-0.29.master.el8ev
When importing the vm from SD which was previously detached, renamed the vm, and verified that it was imported with a new name.
Comment 2 Sandro Bonazzola 2020-05-20 20:03:13 UTC 
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.