Created attachment 1155037 [details] engine logs Description of problem: In V3, when sending a search request for clusters, an empty object is returned Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. /ovirt-engine/api/clusters;max=-1;case_sensitive=false?search=name%3DGolden_Env 2. 3. Actual results: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <clusters/> Expected results: list of clusters Additional info: attached logs - it happened around 18:18
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
I can't reproduce this in my environment. However I see in the attached logs some SQL errors, for example: ERROR: insert or update on table "host_device" violates foreign key constraint "fk_host_device_parent_name" Detail: Key (host_id, parent_device_name)=(19d32811-c8dc-4eca-8d09-497d75899165, scsi_host36) is not present in table "host_device". Could it be that due to previous errors the cluster wasn't really created? I also see in the log another API problem with the top level /permissions resource. I will fix that. May that failure abort the test so that the cluster isn't created?
Note that the proposed patch fixes the issue with the system permissions resource, but as I can't reproduce the original problem in my environment I can't say that it really fixes the issue.
Moving to first RC, since things should not be targeted to second one at this point.
We are actually not creating the clusters during the tests, but running on a pre-existing environment with 2 clusters matching this regex, so I cannot imagine such situation and the clusters still existed at the end of the execution I will try to manually reproduce and update
As it is not clear if the proposed fix solves the issue, I'm moving the bug back to ASSIGNED, and re-setting the need info. Nelly, please clear the need info when/if you are able to reproduce.
The problem is that the value of the "case_sensitive" parameter is ignored, so the following request: /clusters;max=-1;case_sensitive=false?search=name%3DGolden_Env%2A Was looking for clusters named exactly, including case, Golden_Env*, and the clusters in that environment have lower case names, like "golden_env_mixed_1" and "golden_env_mixed_2". The proposed patch fixes this regression.
oVirt 4.0.0 has been released, closing current release.