action #97733
closed
Bot fails on Failed to query latest publiccloud tools image using {settings['PUBLICCLOUD_TOOLS_IMAGE_QUERY']} and no aggregates are scheduled
Added by pdostal over 2 years ago.
Updated over 2 years ago.
Description
Here is example of failing run.
The PUBLICCLOUD_TOOLS_IMAGE_QUERY variable is set to https://openqa.suse.de/group_overview/276.json.
This variable is used as parameter to get_latest_tools_image function which then returns publiccloud_tools_0020.qcow2.
- Priority changed from Normal to Urgent
- Assignee set to okurz
- Target version set to Ready
Initial investigation¶
Subsequent run successfully scheduled at least the rest of the jobs, the public cloud error remains, now with a more specific error message:
ERROR: Failed to query latest publiccloud tools image using https://openqa.suse.de/group_overview/276.json
- Status changed from New to Resolved
- Assignee changed from okurz to jbaier_cz
- Status changed from Resolved to Feedback
- Status changed from Feedback to Resolved
I see several improvements here we can probably evaluate:
- The CI pipeline is still not yet ideal. As there are a lot of runs, we are hitting https://progress.opensuse.org/issues/96827 quite often, that unfortunately hides some of the problems.
- For public cloud, there are at least three different prefixes for variables:
PUBLICCLOUD_, PUBLIC_CLOUD, PC_; that should be unified.
- It would be nice to have at least a basic test suite to better distinguish between metadata error and code error.
- Assignee deleted (
jbaier_cz)
- Target version deleted (
Ready)
jbaier_cz wrote:
- For public cloud, there are at least three different prefixes for variables:
PUBLICCLOUD_, PUBLIC_CLOUD, PC_; that should be unified.
I created #97742 for this.
The bug was in public cloud specific part of the bot but it was affecting all aggregates.
Thank you @jbaier_cz for the fix!
- Assignee set to jbaier_cz
- Target version set to Ready
Also available in: Atom
PDF