Project

General

Profile

Actions
Copy link

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 5 months ago. Updated 23 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
robert.richardson
Category:
Feature requests
Target version:
Ready
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

bare-metal3-broken

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

Download all files
bare-metal3-broken.png (141 KB) bare-metal3-broken.png Julie_CAO, 2024-07-17 08:52
Screenshot From 2024-12-02 21-17-21.png (50 KB) Screenshot From 2024-12-02 21-17-21.png high load rewording example robert.richardson, 2024-12-03 07:40
Actions
Copy link
 #2

Updated by okurz 5 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.

Actions
Copy link
 #3

Updated by Julie_CAO 5 months ago

ok, thanks. My job was not asigned at that moment. Now my job is running.https://openqa.suse.de/tests/14950082#

Actions
Copy link
 #4

Updated by okurz 3 months ago

  • 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
Actions
Copy link
 #5

Updated by okurz 3 months ago

  • Project changed from openQA Infrastructure (public) to openQA Project (public)
  • Category changed from Feature requests to Feature requests
Actions
Copy link
 #6

Updated by okurz about 1 month ago

  • Target version changed from Tools - Next to Ready
Actions
Copy link
 #7

Updated by xlai about 1 month ago

@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 :)

Actions
Copy link
 #8

Updated by robert.richardson 28 days ago

  • Status changed from Workable to In Progress
  • Assignee set to robert.richardson
Actions
Copy link
 #9

Updated by openqa_review 28 days ago

  • Due date set to 2024-12-12

Setting due date based on mean cycle time of SUSE QE Tools

Actions
Copy link
 #10

Updated by robert.richardson 23 days ago

This PR follows the suggestions by rewording the state and error pop up message seen in the tickets description within the WebUI. (merged)

high load rewording example

Actions
Copy link
 #11

Updated by okurz 23 days ago

  • Due date deleted (2024-12-12)
  • Parent task set to #157345
Actions
Copy link

Also available in: Atom PDF