[tools][openqa-monitoring] no products found, retrying version wildcard
|Target version:||Current Sprint|
[Tue Mar 28 07:09:40 2017] [31798:warn] no products found, retrying version wildcard [Tue Mar 28 06:21:26 2017] [25543:warn] no products found, retrying version wildcard [Tue Mar 28 05:50:48 2017] [14721:warn] no products found, retrying version wildcard [Tue Mar 28 05:50:49 2017] [14721:warn] no products found, retrying version wildcard [and many more…]
Not sure about the true meaning of this warning but it's lack of information makes this warning almost useless anyway.
Since this is now a known issue, I'll provide a PR for the logwarn-script of okurz to ignore this warning.
#4 Updated by mkittler about 1 year ago
Not sure about the true meaning of this warning
It means that an ISO has been posted via the REST API and for the given combination of version, distri, flavor and arch no products could be found. Hence the API tried to find products regardless of the specified version (taking only distri, flavor and arch into account). If that would also not yield any products a real failure would be logged.
@coolo Is this weird behavior of ignoring search parameters on mismatch really needed? I mean, why would one create such a strange API and not simply let the client retry the search?
I'd say this weird behavior should go away and errors of that API should be propagated to the other end and not logged on the server. That should be easy to implement. But how does the client look like? Would it display/log the error then?