Actions
action #23378
closed[tools][sprint 201709.1] Enhancement and cleanup of "assigned" state
Start date:
2017-08-14
Due date:
% Done:
0%
Estimated time:
Description
When a job is stuck in the new "assigned" state the webUI does not offer a cancel button, it does not state when it was created or which worker it is assigned to. So "restart the worker" is not so easy when one does not know which worker.
Updated by okurz over 6 years ago
- Copied from action #23364: Leap 42.2 aggregates tests not firing added
Updated by okurz over 6 years ago
- Related to action #23320: [tools][sprint 201709.2][sprint 201710.1][sprint 201710.2] move locks/mutexes/barriers/job restarts out of scheduler added
Updated by okurz over 6 years ago
- Related to action #20378: [tools]Too many 502 on openqa added
Updated by EDiGiacinto over 6 years ago
- Assignee changed from EDiGiacinto to szarate
Spoken on IRC with Santi, he will take care of that in https://github.com/os-autoinst/openQA/pull/1446.
As noted by coolo, js needs some love too, something along the lines of : https://github.com/os-autoinst/openQA/pull/1447
Updated by EDiGiacinto over 6 years ago
- Status changed from New to In Progress
- Assignee changed from szarate to EDiGiacinto
Updated by EDiGiacinto over 6 years ago
- Status changed from In Progress to Resolved
Updated by szarate over 6 years ago
- Subject changed from Enhancement and cleanup of "assigned" state to [tools][sprint 201709.1] Enhancement and cleanup of "assigned" state
Actions