Description of problem:
As we plan to remove v3 of the oVirt API in oVirt 4.2, we need all the requests to go through v4 of the oVirt API.
Moving to verified on CFME-220.127.116.11/RHV-18.104.22.168,
based on the automation+manual testing done with the changes to V4.
Only the operations that V4 is activated for them by default were tested.
The New features, that the V4 option is not activated for them, were not tested with V4 yet.
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.
Pre testing done with switching to oVirt API V4, on RHV-22.214.171.124/CFME-126.96.36.199:
1. Automation tests PASSED.
2. Manual tests:
a. VM provision (Native/ISO/PXE) - PASS, except for PXE bug 1454861
b. VM reconfigure - PASS
c. Provider full refresh - PASS
d. Refresh of PXE server - PASS
e. Refresh of iso domain - PASS
f. Refresh of VM’s snapshots, disks, power status, memory, cpu - PASS
These tests were run as a preparation to CFME-5.8.1, where oVirt API is planned to change from V3 to V4.