action #164084
closed
coordination #154768: [saga][epic][ux] State-of-art user experience for openQA
coordination #157345: [epic] Improved test reviewer user experience
machines with "load too high" show up as broken which confuses users size:S
Added by Julie_CAO 9 months ago.
Updated 5 months ago.
Category:
Feature requests
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
- 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.
- Subject changed from bare-metal3 is seen broken on OSD web UI aka. "load too high" to machines with "load too high" show up as broken which confuses users size:S
- Description updated (diff)
- Status changed from New to Workable
- Project changed from openQA Infrastructure (public) to openQA Project (public)
- Category changed from Feature requests to Feature requests
- Target version changed from Tools - Next to Ready
@okurz This is related to recent NUE2 cc isolation, we've lost almost half ipmi workers, so the workload on usable machines is very high. Hope this can be some data to support bumping priority of finding solutions for NUE2 ipmi baremetal machines :)
- Status changed from Workable to In Progress
- Assignee set to robert.richardson
- Due date set to 2024-12-12
Setting due date based on mean cycle time of SUSE QE Tools
This PR follows the suggestions by rewording the state and error pop up message seen in the tickets description within the WebUI. (merged)
- Due date deleted (
2024-12-12)
- Parent task set to #157345
Also available in: Atom
PDF