Bug 2071488 - "Migrate Node to Node" is confusing.
Summary: "Migrate Node to Node" is confusing.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.11.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 4.11.0
Assignee: Aviv Turgeman
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-04 04:07 UTC by Germano Veit Michel
Modified: 2023-11-13 08:19 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-14 19:29:36 UTC
Target Upstream Version:
Embargoed:
aguetta: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt-ui kubevirt-plugin pull 333 0 None open Bug 2071488: "Migrate Node to Node" is confusing. 2022-04-27 10:05:46 UTC
Github kubevirt-ui kubevirt-plugin pull 408 0 None open Bug 2071488: "Migrate Node to Node" is confusing. 2022-05-11 13:57:14 UTC
Red Hat Issue Tracker CNV-17828 0 None None None 2023-11-13 08:19:36 UTC
Red Hat Product Errata RHSA-2022:6526 0 None None None 2022-09-14 19:30:45 UTC

Description Germano Veit Michel 2022-04-04 04:07:51 UTC 
Description of problem:

In Virtualization -> Virtual Machines click on the more options (3 vertical dots) for one of the VMs. One option is called "Migrate Node to Node"

Previously this was "Migrate Virtual Machine to Node" (4.9). Now its "Migrate Node to Node in 4.10, which is wrong and confusing.
Comment 3 Yaacov Zamir 2022-04-27 16:58:30 UTC 
Aviv hi,
a nicer fix can be to use the description in the actions
so the action name will be "Migrate" like "Start/Pause ..."
and the action description be more verbose "Migrate the virtual machine to a different node"
WDYT?
Comment 4 Aviv Turgeman 2022-04-28 07:42:42 UTC 
Hi Yaacov, 

I like your suggestion and think it makes sense,
do we need to approve this with PM/UX?
Comment 5 Yaacov Zamir 2022-04-28 08:25:52 UTC 
> do we need to approve this with PM/UX?

yes :-)
Comment 6 Guohua Ouyang 2022-05-05 01:09:19 UTC 
What do you think if we move it back to "Migrate Virtual Machine to Node" or do you have a good suggestion? :)
Comment 7 Germano Veit Michel 2022-05-05 01:11:33 UTC 
(In reply to Guohua Ouyang from comment #6)
> What do you think if we move it back to "Migrate Virtual Machine to Node" or
> do you have a good suggestion? :)

Just "Migrate" please. From the context the user is already clicking on the options for a VM, and it can only migrate to "Nodes".
Comment 8 Guohua Ouyang 2022-05-05 01:41:45 UTC 
Can we change the action to "Migrate" based on c#3 and c#7?
Comment 9 Aviv Turgeman 2022-05-08 09:23:01 UTC 
moving back to assigned based on c#3, c#7, and c#8
Comment 10 Yifat Menchik 2022-05-15 10:51:34 UTC 
I agree with comment 3 meaning the action should be "Migrate" as all the other actions we have in this dropdown. The descriptive text below the action should explain what is migrating: something like "Migrate the virtual machine to a different node". 
We can also advise the docs team about the exact copy for the descriptive text.
Comment 11 Guohua Ouyang 2022-05-19 01:39:13 UTC 
verified on v4.11.0-369
Comment 14 errata-xmlrpc 2022-09-14 19:29:36 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Virtualization 4.11.0 Images security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:6526
Note You need to log in before you can comment on or make changes to this bug.