Actions
action #164084
openmachines with "load too high" show up as broken which confuses users size:S
Start date:
2024-07-17
Due date:
% Done:
0%
Estimated time:
Description
Observation¶
Don't know what happend to the machine? Could you please help to fix it?
https://openqa.suse.de/admin/workers/2695
Acceptance criteria¶
- AC1: The worker state reports something better than "broken" when just the load is too high
- AC2: The worker still reports in other cases that admins need to act
Suggestions¶
- Try to distinguish the state or maybe we can just find a better wording?
- Brainstorming alternatives: "Unavailable"
- Replace the title in the popup to not say "Error" but maybe "Details"?
- Reconsider the detailed texts to clearly indicate what the viewer should do or not do
Files
Updated by okurz 4 months ago
- Subject changed from bare-metal3 is seen broken on OSD web UI to bare-metal3 is seen broken on OSD web UI aka. "load too high"
- Category set to Feature requests
- Target version set to Tools - Next
well, there is nothing wrong. The worker reports itself as "broken" due too a temporarily too high load on the worker so jobs are waiting until the load is lower again. Then jobs will be picked up automatically. The state "broken" can be misleading and we should consider to either rename that or declare a new state.
Updated by Julie_CAO 4 months ago
ok, thanks. My job was not asigned at that moment. Now my job is running.https://openqa.suse.de/tests/14950082#
Updated by okurz about 1 month ago
- Project changed from openQA Infrastructure to openQA Project
- Category changed from Feature requests to Feature requests
Actions