QA » openQA Project

I also did some tests in local, have different result:

./client --json-output --host https://openqa.suse.de --apibase / group_overview/263 limit_builds=1
null

I used /openqa-cli api --osd --apibase / group_overview/263 limit_builds=1 --json, it could get the results, but the format is html. not a json data.

I guess the related pr is: https://github.com/os-autoinst/openQA/pull/3820

Maybe related to https://github.com/mojolicious/mojo/wiki/Upgrading#format-detection-disabled-by-default

However, since 2 PRs to handle it have been merged, it shouldn't be a problem anymore. Accessing e.g. https://openqa.suse.de/tests/overview.json?distri=sle&version=15-SP3&build=172.3&groupid=110 within the browser also returns JSON. The following works as well:

openqa-cli api --osd --apibase / group_overview/263.json limit_builds=1

So just be sure to use the .json extension.

(Note that --json is for setting the content type if you want to upload a JSON document and shouldn't influence the response.)

mkittler wrote:

openqa-cli api --osd --apibase / group_overview/263.json limit_builds=1

So just be sure to use the .json extension.

Actually, the .json extension should not even be necessary with openqa-cli api. It always sets the Accept: application/json header (as long as you don't override it with your own Accept header).

kraih wrote:

Actually, the .json extension should not even be necessary with openqa-cli api. It always sets the Accept: application/json header (as long as you don't override it with your own Accept header).

I was wrong with that unfortunately. The workaround we use in the routes always sets the default extension to .html, which make the Accept header do nothing. So content negotiation is kinda broken at the moment.

Is this something that could be addressed on Mojolicious-level (assuming openQA's code is supposed to work)?

Only solution i can think of would require us to depend on Mojolicious 9.11+. I've already prepared a PR. https://github.com/os-autoinst/openQA/pull/3830

Shouldn't --apibase / actually cause an error? It makes no sense to point it at anything that's not openQA-compatible RESTful API. At least I don't see what the purpose of that would be

okurz wrote:

Basically the same as in #88363 applies:

So what you are doing with the parameter --apibase / is basically not using the intended web API at all

What is the intended web api(restapi) that client script supports to get group overview json format output?

but instead retrieve the web pages that are meant for consumption by browsers and human readers. If you want to have a machine readable representation of the "group overview" page in JSON format you can use for example

curl -s https://openqa.opensuse.org/group_overview/1.json

Both openqa-client and openqa-cli are not meant and not necessary to access these pages. Good enough?

@okurz Thanks for the comment.

I can switch to use /usr/share/openqa/script/client ... group_overview/1.json, and it works in my environment.

xlai wrote:

okurz wrote:

Basically the same as in #88363 applies:

So what you are doing with the parameter --apibase / is basically not using the intended web API at all

What is the intended web api(restapi) that client script supports to get group overview json format output?

The default is /api/v1 which is the RESTful openQA API. This is why I'm surprised it doesn't cause an error - this is not just a path

cdywan wrote:

xlai wrote:

okurz wrote:

Basically the same as in #88363 applies:

So what you are doing with the parameter --apibase / is basically not using the intended web API at all

What is the intended web api(restapi) that client script supports to get group overview json format output?

The default is /api/v1 which is the RESTful openQA API. This is why I'm surprised it doesn't cause an error - this is not just a path

@cdywan But why from my trying, it does not work to use apibase /api/v1(I hide my api key/secret when paste)?

qa2-dhcp-53:~ # /usr/share/openqa/script/client --json-output --host http://openqa.nue.suse.com --apikey --apisecret --apibase /api/v1 group_overview/263 limit_builds=1
ERROR: 404 - Not Found

{ error_status => 404 }

qa2-dhcp-53:~ # /usr/share/openqa/script/client --json-output --host http://openqa.nue.suse.com --apikey --apisecret --apibase /api/v1 group_overview/263

ERROR: 404 - Not Found

{ error_status => 404 }

qa2-dhcp-53:~ # /usr/share/openqa/script/client --host http://openqa.nue.suse.com ---apikey --apisecret --apibase /api/v1 group_overview/263
ERROR: 404 - Not Found

{ error_status => 404 }
qa2-dhcp-53:~ # /usr/share/openqa/script/client --host http://openqa.nue.suse.com --apikey --apisecret --apibase api/v1 group_overview/263
ERROR: 404 - Not Found
{ error_status => 404 }
qa2-dhcp-53:~ # /usr/share/openqa/script/client --host http://openqa.nue.suse.com --apikey --apisecret --apibase api/v1 group_overview/263.json
ERROR: 404 - Not Found
{ error_status => 404 }
qa2-dhcp-53:~ #

xlai wrote:

okurz wrote:

Basically the same as in #88363 applies:

So what you are doing with the parameter --apibase / is basically not using the intended web API at all

What is the intended web api(restapi) that client script supports to get group overview json format output?

There is none. Because the group overview in the same way you want to get it is not an "API call" per se but a JSON representation of the html page which you can get with curl in the way I described. No need to use the openqa-client.

xlai wrote:

cdywan wrote:

xlai wrote:

okurz wrote:

Basically the same as in #88363 applies:

So what you are doing with the parameter --apibase / is basically not using the intended web API at all

What is the intended web api(restapi) that client script supports to get group overview json format output?

The default is /api/v1 which is the RESTful openQA API. This is why I'm surprised it doesn't cause an error - this is not just a path

@cdywan But why from my trying, it does not work to use apibase /api/v1(I hide my api key/secret when paste)?

qa2-dhcp-53:~ # /usr/share/openqa/script/client --json-output --host http://openqa.nue.suse.com --apikey --apisecret --apibase /api/v1 group_overview/263 limit_builds=1
ERROR: 404 - Not Found

{ error_status => 404 }

qa2-dhcp-53:~ # /usr/share/openqa/script/client --json-output --host http://openqa.nue.suse.com --apikey --apisecret --apibase /api/v1 group_overview/263

ERROR: 404 - Not Found

{ error_status => 404 }

qa2-dhcp-53:~ # /usr/share/openqa/script/client --host http://openqa.nue.suse.com ---apikey --apisecret --apibase /api/v1 group_overview/263
ERROR: 404 - Not Found

{ error_status => 404 }
qa2-dhcp-53:~ # /usr/share/openqa/script/client --host http://openqa.nue.suse.com --apikey --apisecret --apibase api/v1 group_overview/263
ERROR: 404 - Not Found
{ error_status => 404 }
qa2-dhcp-53:~ # /usr/share/openqa/script/client --host http://openqa.nue.suse.com --apikey --apisecret --apibase api/v1 group_overview/263.json
ERROR: 404 - Not Found
{ error_status => 404 }
qa2-dhcp-53:~ #

Because these API routes do not exist. https://openqa.nue.suse.com/what_are_supported_api_routes lists all existing paths for both the real API routes (below /api/v1) as well as the ones that are used internally as well as those pages that can be accessed directly (e.g. /tests).

Further hints:

• Put your API keys and secrets in ~/.config/openqa/client.conf, do not append apikey and apisecret parameter. Then you are also not running into risk into copy-pasting them into a ticket comment :)
• apibase "/api/v1" is the implicit default. Better don't use the apibase parameter, there is currently no good use case for that. Likely this parameter was introduced to allow switching to a different API version but so far we have only a single one
• Use openqa-client from PATH instead of a full path /usr/share/openqa/script/client
• Consider using openqa-cli api --osd instead of openqa-client --host http://openqa.nue.suse.com

@okurz, thanks for the detailed reply.