Description of problem:
In RHEV4, the API endpoint has moved from:
$HOSTNAME/api
to
$HOSTNAME/ovirt-engine/api/
Version-Release number of selected component (if applicable):
virt-who-0.17-11.el7_3.noarch
How reproducible:
100%
Steps to Reproduce:
1. install virt-who.
2. Configure it as per the docs (either https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/virtual-instances-guide#configuring_virt_who_to_connect_to_red_hat_enterprise_virtualization_hypervisor or via the instructions in the virt-who manual.
3. run virt-who
Actual results:
Virt-who fails to gather host/guest mappings and fails with an error similar to the following.
2017-01-22 11:48:37,083 [virtwho.rhev-farm ERROR] RhevM-2(11346):MainThread @virt.py:run:375 - Virt backend 'rhev-farm' fails with error: Unable to connect to RHEV-M server: 404 Client Error: Not Found
Expected results:
Successful virt-who report.
Additional info:
Configuring virt-who with /ovirt-engine/ appended to the server= directive allows a successful report as shown below:
$ cat /etc/virt-who.d/rhev.conf
[rhev-farm]
# type = esx,rhevm,kvm
type=rhevm
# server = vcenter OR individual ESXi host
# Works with RHV4
server=https://rhevm.example.com:443/ovirt-engine/
# Does NOT work with RHV4
# server=https://rhevm.example.com:443/
This _could_ be treated as a docs BZ, but ideally, I'd like virt-who to try both API endpoints and use whichever works (as there will be users upgrading from RHEV3 to RHV4, and I'd like virt-who to 'just work' post upgrade).
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-2017:2084