Created attachment 1492950 [details] REST Client Description of problem: Got HTTP error 404 or 'EntityNotFound' while trying to fetch vnicprofile object via REST API Version-Release number of selected component (if applicable): 4.3.0-0.0.master.20181010155922.gite89babf.el7 How reproducible: 100% Steps to Reproduce: 1. Open: https://[engine_fqdn]/ovirt-engine/api/networks 2. Try to open one of the following links: 'permissions', 'vnicprofiles', 'networklabels' for one of the Networks Actual results: Got HTTP error 404 Links point as followed: /ovirt-engine/api/datacenters/[DC_ID]/networks/[NETWORK_ID]/vnicprofiles Expected results: 200 Ok! /ovirt-engine/api/networks/[NETWORK_ID]/vnicprofiles Additional info: See also attached screen capture of REST client results
The reason for the bug is actually a proper repair done to the repository of static data about the API structure, used for link-generation purposes. This data was manually maintained by developers, and thus contained many errors. This patch: https://gerrit.ovirt.org/#/c/82294/ made the repository 100% correct by replacing the human maintenance with automatic data mining. However in some cases, the result of the repository containing the correct data broke backwards compatibility, in places where particular implementations 'counted on' the repository being wrong, containing a bug (2 wrongs make a right). Analyzing the data in the old vs new and updated repositories, the above problem is expected to happen also for iscsibond networks, and thus this has been addressed as well.
With the patch merged, shouldn't this move to MODIFIED?
Verified on - ovirt-engine-4.3.0-0.0.master.20181030100636.git6215452.el7.noarch
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.