Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1359149[details]
screenshot for direct migration and tunnelled migration are same now.
Description of problem:
Improve description for direct migration and tunnelled migration
Version-Release number of selected component (if applicable):
virt-manager-1.4.3-2.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1. Launch virt-manager
2. Select a guest then right click it, migrate it from source host to target host.
3. On the migration configuration page, move the cursor above direct mode, check the tooltip.
4. Repeat step3, then move the cursor above tunnelled mode, and also check the tooltip.
Actual results:
Tooltip for step3 and step4 are same.
Expected results:
Description for direct migration and tunnelled migration should be different.
Additional info:
So the tooltip was not intended as a documentation for each migration mode. It doesn't have to change if the tooltip describes both modes at the same time.
If you read carefully the first sentence it basically describes a difference between the tunneled and direct, but I agree that the tooltip can be improved, however, it is a minor issue and probably no need to fix it. I'm closing this bug as WONTFIX.
Created attachment 1359149 [details] screenshot for direct migration and tunnelled migration are same now. Description of problem: Improve description for direct migration and tunnelled migration Version-Release number of selected component (if applicable): virt-manager-1.4.3-2.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Launch virt-manager 2. Select a guest then right click it, migrate it from source host to target host. 3. On the migration configuration page, move the cursor above direct mode, check the tooltip. 4. Repeat step3, then move the cursor above tunnelled mode, and also check the tooltip. Actual results: Tooltip for step3 and step4 are same. Expected results: Description for direct migration and tunnelled migration should be different. Additional info: