Bug 1520455 - The VM name resets to original value when switching tab in 'import virtual machine' dialog
Summary: The VM name resets to original value when switching tab in 'import virtual ma...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.3.0
: 4.3.0
Assignee: Eyal Shenitzky
QA Contact: Yosi Ben Shimon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-04 13:57 UTC by Yosi Ben Shimon
Modified: 2019-02-13 07:46 UTC (History)
6 users (show)

Fixed In Version: ovirt-engine-4.3.0_alpha
Clone Of:
Environment:
Last Closed: 2019-02-13 07:46:43 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.3+
ylavi: exception+


Attachments (Terms of Use)
screenshot of the Import VM dialog window (512.10 KB, image/gif)
2017-12-04 13:57 UTC, Yosi Ben Shimon
no flags Details
Import VM dialog (1.22 MB, image/gif)
2018-02-25 14:43 UTC, Yosi Ben Shimon
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 87514 0 master MERGED webadmin: keep edited imported VM name while moving through tabs 2018-02-13 13:34:31 UTC
oVirt gerrit 87542 0 ovirt-engine-4.2 MERGED webadmin: keep edited imported VM name while moving through tabs 2018-02-13 13:35:49 UTC
oVirt gerrit 88765 0 master MERGED webadmin: map edited VM name while importing VMs 2018-04-01 09:15:49 UTC
oVirt gerrit 89646 0 ovirt-engine-4.2 ABANDONED webadmin: map edited VM name while importing VMs 2018-04-01 09:23:26 UTC

Description Yosi Ben Shimon 2017-12-04 13:57:40 UTC
Created attachment 1362694 [details]
screenshot of the Import VM dialog window

Description of problem:
The VM name resets to original value when switching tab in 'import virtual machine' dialog window.

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.5.master.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. Enter 'VM Import' tab under Export storage domain.
2. Select VM.
3. Click 'Import' button on the right side.
4. Click on the VM row to open the configuration below.
5. Set VM name.
6. Switch to any other tab.
7. Switch back to 'general' tab.

Actual results:
The VM name resets to original value.

Expected results:
The VM name value should be the new name.

Additional info:

Comment 1 Yaniv Kaul 2017-12-05 05:40:28 UTC
Rephrase title please

Comment 2 Tal Nisan 2017-12-05 08:19:36 UTC
Benny, this might have been caused by your fix to bug 1449515, please have a look

Comment 3 Yosi Ben Shimon 2017-12-12 12:59:16 UTC
Title rephrased.
Removing NeedInfo

Comment 4 Yosi Ben Shimon 2018-02-25 14:43:53 UTC
Created attachment 1400573 [details]
Import VM dialog

Comment 5 Yosi Ben Shimon 2018-02-25 14:44:14 UTC
Tested using:
ovirt-engine-4.2.2.1-0.1.el7.noarch

Actual result:
- The name of the VM stays the same when switching tabs.
- The name of the VM stays the same even after cancelling.

See attached screen capture.

Moving to ASSIGNED

Comment 6 Yosi Ben Shimon 2018-08-19 13:13:08 UTC
Tested using:
ovirt-engine-4.3.0-0.0.master.20180815091554.gitd5455ea.el7.noarch

Actual result:
- The name of the VM stays the same when switching tabs as expected.
- The name of the VM resets after cancelation as expected.

Moving to VERIFIED

Comment 7 Sandro Bonazzola 2018-11-02 14:32:57 UTC
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 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.

Comment 8 Sandro Bonazzola 2018-11-02 14:50:46 UTC
Closed by mistake, moving back to qa -> verified

Comment 9 Sandro Bonazzola 2019-02-13 07:46:43 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.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.