action #173689
closed
[openQA][worker][ipmi] Scheduled test run using ipmi worker can not be assigned to idle workers
Added by waynechen55 15 days ago.
Updated 15 days ago.
Description
Observation¶
Triggered test run by using openqa-clone-custom-git-refspec which returns
https://openqa.suse.de/tests/16089795
https://openqa.suse.de/tests/16089796
But these two test runs never start because no ipmi worker is assigned.
I found there are many idle ipmi workers:
Steps to reproduce¶
- Schedule test run using ipmi worker
- Wait for it to be assigned to worker
Impact¶
Can not run test
Problem¶
Looks like schedule or worker service issue
Suggestions¶
- Check openQA schedule service
- Check openQA worker service
- Check worker settings
- Check connection between worker and openQA
Workaround¶
n/a
Files
- Tags set to infra
- Category set to Support
- Status changed from New to Feedback
- Assignee set to okurz
- Target version set to Ready
Hi, both tests
https://openqa.suse.de/tests/16089795
https://openqa.suse.de/tests/16089796
are removed by now. I assume they were blocking SLE maintenance updates and somebody removed them to unblock? I assume that the tests were scheduled with a worker class that isn't fulfilled by the available workers. Could that be? Can you show the command line with which you triggered jobs?
- Due date set to 2024-12-18
okurz wrote in #note-1:
Hi, both tests
https://openqa.suse.de/tests/16089795
https://openqa.suse.de/tests/16089796
are removed by now. I assume they were blocking SLE maintenance updates and somebody removed them to unblock? I assume that the tests were scheduled with a worker class that isn't fulfilled by the available workers. Could that be? Can you show the command line with which you triggered jobs?
They were assigned and started running later after quite a period. And sorry I removed them by myself after some unexpected test run failures.
- Due date deleted (
2024-12-18)
- Status changed from Feedback to Resolved
Sorry, without the job settings nor command line details I don't think we can help more. Please bring the topic up again if you encounter similar problems. Until then I assume you used a worker class that is not fulfilled by any currently running worker instances.
Also available in: Atom
PDF