Description of problem: Running $(curl -v -u "$user@$domain:$password" -H "Content-type: application/xml" -H "Version: 3" --insecure -X GET https://$fqdn/ovirt-engine/api/capabilities | grep "<version major") results in only 3.6, 4.0 and 4.1 versions being printed: <version major="3" minor="6" href="/ovirt-engine/api/capabilities/332e3633-2e36-332e-3633-2e36332e3633" id="332e3633-2e36-332e-3633-2e36332e3633"> <version major="4" minor="0" href="/ovirt-engine/api/capabilities/332e4033-2e40-332e-4033-2e40332e4033" id="332e4033-2e40-332e-4033-2e40332e4033"> <version major="4" minor="1" href="/ovirt-engine/api/capabilities/332e4133-2e41-332e-4133-2e41332e4133" id="332e4133-2e41-332e-4133-2e41332e4133"> where when using v4 API $(curl -v -u "$user@$domain:$password" -H "Content-type: application/xml" -H "Version: 4" --insecure -X GET https://$fqdn/ovirt-engine/api/clusterlevels | grep "<cluster_level") I get all supported versions (3.6, 4.0, 4.1 and 4.2): <cluster_level href="/ovirt-engine/api/clusterlevels/4.2" id="4.2"> <cluster_level href="/ovirt-engine/api/clusterlevels/4.1" id="4.1"> <cluster_level href="/ovirt-engine/api/clusterlevels/4.0" id="4.0"> <cluster_level href="/ovirt-engine/api/clusterlevels/3.6" id="3.6"> There should be version 4.2 when using v3 API as well. Version-Release number of selected component (if applicable): ovirt-engine-4.2.0-0.0.master.20171025204923.git6f4cbc5.el7.centos.noarch How reproducible: always Steps to Reproduce: 1. curl -v -u "$user@$domain:$password" -H "Content-type: application/xml" -H "Version: 3" --insecure -X GET https://$fqdn/ovirt-engine/api/capabilities | grep "<version major" Actual results: There is no version 4.2 Expected results: There should be version 4.2 Additional info:
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [No relevant external trackers attached] For more info please contact: infra
Verified that version 4.2 is in capabilities for REST API version 3. Engine Version 4.2.0-0.0.master.20171108151837.gita7de53e.el7.centos
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.