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.
Cause: remote-viewer did not take into account proxy information returned through RHEV REST API
Consequence: when using ovirt:// , it was not possible to connect to VMs behind a proxy
Fix: get proxy information from RHEV REST API
Result: it's possible to connect to VMs behind a proxy when using ovirt:// URIs
Comment 15Christophe Fergeau
2016-01-07 13:58:46 UTC
I made the same confusion as usual, 'proxy-url' will be used when accessing the VM through ovirt://
Setup:
- the ovirt portal can be accessed without a proxy (I'm not sure how to tell libgovirt to use a proxy, maybe it can use the http_proxy environment variable)
- the VM must only be accessible through a proxy
- run remote-viewer ovirt://rhev-portal.example.com/vm-name
expected result: remote-viewer should access the VM named 'vm-name' using the proxy
I can reproduce it.
# rpm -q libgovirt virt-viewer
libgovirt-0.3.2-2.el6.x86_64
virt-viewer-2.0-8.el6.x86_64
Steps:
1. Setup an env and make sure you can connect to ovirt directly but can't connect to vm directly.
2. configure a proxy, make sure you can connect to vm by the proxy.
3. get the ca.crt file from ovirt.
# wget https://ibm-x3250m5-03.qe.lab.eng.nay.redhat.com/ca.crt
4. connect the vm by ovirt.
# remote-viewer --ovirt-ca-file=ca.crt ovirt://ibm-x3250m5-03.qe.lab.eng.nay.redhat.com/$vm
Result:
Can see remote-viewer window pops up and "change cd" menu displays but connect to the vm fail.
Updated virt-viewer to version virt-viewer-2.0-12.el6.x86_64 and verified it again.
can see the foreign menu and can connect to the vm successfully.
So move the bug 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://rhn.redhat.com/errata/RHBA-2016-0832.html