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.
Description of problem:
ovirt uri cannot be saved after connecting to guest successfully.
Version-Release number of selected component (if applicable):
virt-viewer-5.0-7.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Run "remote-viewer --ovirt-ca-file=xxx ovirt://xxxx/xxxx" to connect to a guest succesfully.
2. Run "remote-viewer --ovirt-ca-file=xxx", check the recent connections in recent dialog.
Actual results:
The ovirt uri is not listed in recent dialog.
Expected results:
The ovirt uri should be listed in recent dialog.
Additional info:
Now there is a problem, when the guest specified in ovirt url doesn't exist in rhevm, a dialog will pop up and ask you to select one if rhevm has running guests. And then if you select one and connect to it successfully, remote-viewer will remember the wrong ovirt url.
You can ignore the invalid url or correct the wrong guest name to the guest name you selected.
I prefer to correct it automatically.
Comment 11Eduardo Lima (Etrunko)
2017-11-22 18:14:24 UTC
(In reply to xiaodwan from comment #10)
> Now there is a problem, when the guest specified in ovirt url doesn't exist
> in rhevm, a dialog will pop up and ask you to select one if rhevm has
> running guests. And then if you select one and connect to it successfully,
> remote-viewer will remember the wrong ovirt url.
>
> You can ignore the invalid url or correct the wrong guest name to the guest
> name you selected.
>
> I prefer to correct it automatically.
This is something to think about, some similar use cases could be:
1) There is no VM specified with the URI. This will also show the VM selection dialog and should we save the URI as specified by the command line or include the selected VM?
2) VM exists but is down, the selection dialog will also be shown, and if user selects different VM?
3) Username is specified in the URI, but user changes it in the dialog asking for the password, which should be saved?
The problem in this bug has been fixed in virt-viewer-5.0-9.el7.x86_64.
For other problems, i filed a new bug to track them.
Bug 1517040 - RFE: improve the logic when saving ovirt url
So move the bug from ON_QA to VERIFIED.
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, 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/RHBA-2018:0672