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:
When monitor rhevm4.0, if server url is not end with "/", virt-who will fail to connect rhevm API.

Version-Release number of selected component (if applicable):
rhevm4.0
virt-who-0.17-2.el7.noarch
subscription-manager-1.17.6-1.el7.x86_64
python-rhsm-1.17.2-1.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Register system to satellite6.2
2.Make virt-who monitor rhevm4.0, make sure server url is not end of "/"
[root@hp-dl2x170g6-01 virt-who.d]# cat /etc/virt-who.d/virt 
[test-rhevm1]
type=rhevm
server=https://hp-z220-13.qe.lab.eng.nay.redhat.com:443/ovirt-engine  ===>No "/"
username=admin@internal
password=redhat
owner=ACME_Corporation
env=Library
3. Restart virt-who and check virt-who's log
2016-06-02 23:48:52,895 [virtwho.test-rhevm1 ERROR] RhevM-1(22567):MainThread @virt.py:run:374 - Virt backend 'test-rhevm1' fails with error: Unable to connect to RHEV-M server: 404 Client Error: Not Found

Actual results:
Virt-who can't send host/guest mapping info to server since it can't get correct API. 
[NOTE]: if "/" at the end of server url, it hasn't this problem

Expected results:
No matter whether server url end with "/" or not, virt-who should get API correctly.

Additional info:

Fixed upstream:

https://github.com/virt-who/virt-who/commit/a5185bc1b26d2f926cf9aa6f38056e841f0d33f8

Fixed in virt-who-0.17-3.el7.

verified in virt-who-0.17-5.el7.noarch

virt-who can work normally with "/" or no "/" for the server URL

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-2387.html