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:
use remote-viewer try to connect ovirt URI, if click "Cancle" button, remote-viewer cannot quit normally

Version-Release number of selected component (if applicable):
virt-viewer-2.0-3.el6.x86_64
libgovirt-0.3.2-1.el6.x86_64

How reproducible:
100

Steps to Reproduce:
1. Prepare rhevm env and a rhel6 guest
2. wget http://rhevm.addr/ca.crt
3. remote-viewer --ovirt-ca-file=ca.crt ovirt://rhevm.addr/guest
(remote-viewer:27104): libgovirt-WARNING **: Passing a full http:// or https:// URI to ovirt_proxy_new() is deprecated

(remote-viewer:27104): libgovirt-WARNING **: Passing an URI ending in /api to ovirt_proxy_new() is deprecated
4. auth dialog comes out, then click cancle button
5. # echo $?


Actual results:
Step 4, get an error dialog:
"Couldn't open oVirt session: Unauthorized"

(remote-viewer:27158): libsoup-CRITICAL **: soup_auth_authenticate: assertion `username != NULL' failed

(remote-viewer:27158): libgovirt-WARNING **: Error while getting collection: Unauthorized
Step5. 
# echo $?
1

Expected results:
remote-viewer should quit without error

Additional info:

patch series: https://www.redhat.com/archives/virt-tools-list/2015-March/msg00095.html

Relevant upstream commit:
https://git.fedorahosted.org/cgit/virt-viewer.git/commit/?id=1bcd8d0fe6df553f087d11b539a59e128a2a350b

Final patch will be based on the review of librest patch: https://bugzilla.gnome.org/show_bug.cgi?id=746537 and libgovirt patch: https://bugzilla.gnome.org/show_bug.cgi?id=746539 

or it can be workaround by https://www.redhat.com/archives/virt-tools-list/2015-March/msg00119.html

(In reply to Pavel Grunt from comment #3)
> Relevant upstream commit:
> https://git.fedorahosted.org/cgit/virt-viewer.git/commit/
> ?id=1bcd8d0fe6df553f087d11b539a59e128a2a350b
> 
> Final patch will be based on the review of librest patch:
> https://bugzilla.gnome.org/show_bug.cgi?id=746537 and libgovirt patch:
> https://bugzilla.gnome.org/show_bug.cgi?id=746539 
> 
> or it can be workaround by
> https://www.redhat.com/archives/virt-tools-list/2015-March/msg00119.html

Moving this to libgovirt as it's better to go with the upstream libgovirt/librest patches rather than the virt-viewer workaround.

The librest bug blocked by this one hasn't been fixed, and we do need this patch in virt-viewer actually
https://git.fedorahosted.org/cgit/virt-viewer.git/commit/?id=0443bd113f8474ca707c7847e2806a6e374e8a21

based on dependency tree moving to the next release

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://rhn.redhat.com/errata/RHBA-2017-0587.html