action #108824
Updated by livdywan about 2 years ago
Some of the tests that are triggered by the bot-ng are cancelled without any apparent reason and missing logs.
Examples:
https://openqa.suse.de/tests/8379473
https://openqa.suse.de/tests/8379476
I have observed this a few times in past days, but I thought it was a sporadic error.
Let's use this ticket to collect these kind of failures.
## Acceptance criteria
- **AC1**: It is clear what the expected scheduling behavior is (e.g. is VERSION *supposed* to be 5.1 in the job despite VERSION 5.0 being specified when scheduling the product)
## Suggestions
- Clarify with the author of the test - this test is very new
- Initial hypothesis: Have these jobs *not* been scheduled by bot-ng?
- Find a way to distinguish bot jobs better
- Find out why affected jobs are scheduled with 5.0 but show VERSION 5.1 in the settings
- https://gitlab.suse.de/qac/qac-openqa-yaml/-/blob/master/sle-micro/updates.yaml#L170
- Examine bot-ng logs for scheduling the sle-micro, look for both 5.0 and 5.1 versions (the other one could obsolete the first one)
- Product log for 5.0 scheduling: https://openqa.suse.de/admin/productlog?id=886973
- Product log for 5.1 scheduling: https://openqa.suse.de/admin/productlog?id=886978
- If the bot cancells jobs as expected, comment "Cancelled because of job #foo" on relevant jobs