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:

Using virt-who in rhevm mode to connect to Version 4.x RHEVM, virt-who still uses V3 APIs which are deprecated by RHEV/Ovirt and following events log in RHEV

" Client from address "X.X.X.X" is using version 3 of the API, which has been deprecated since version 4.0 of the enginer, and will no longer be supported ...."

There is a solution article saying it was fixed but looking at the code, it still attempts to use header "version: 3" first even if it detects that major version at RHEVM is 4 

https://access.redhat.com/solutions/4491051

Version-Release number of selected component (if applicable):
RHEV 4.X
virt-who-0.26.5-1.el7.noarch

How reproducible:

Always

Steps to Reproduce:

make a a virt-who config for a 4.X RHEVM mode and run. Deprecation messages can be seen in Even log at RHEVM


Expected results:
After detecting that rhevm version is 4.x it should attempt a V4 api first or not even use any version header as by default it falls back to V4

Created attachment 1687273 [details]
client_event_log

Created attachment 1699082 [details]
picture_0629

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 (virt-who bug fix update), 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-2020:3865