action #107497
closedcoordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
coordination #109659: [epic] More remote workers
[qe-tools] openqaworker14 (and openqa15) - developer mode fails size:M
0%
Description
Observation¶
in live view developer mode fails and reports fail every 2 sec
from browser javascript console:
Establishing ws connection to wss://openqa.suse.de/liveviewhandler/tests/8210859/developer/ws-proxy/status
Received message via ws proxy: {"data":null,"type":"info","what":"connecting to os-autoinst command server at ws:\/\/10.100.96.68:20043\/OX0bG6w17OkxmWt_\/ws"}
Received message via ws proxy: {"data":null,"type":"error","what":"unable to upgrade ws to command server"}
Error from ws proxy: unable to upgrade ws to command server
Connection to livehandler lost
the connection between osd and workers works without problems and IP address of worker is also correct
Acceptance criteria¶
- AC1: Developer mode on openqaworker14.qa.suse.cz works reliably as part of the productive OSD infrastructure
Suggestions¶
- Follow https://open.qa/docs/#debugdevelmode
- not likely related to known issues with network performance
Files
| Snímek obrazovky 2022-02-22 v 13.35.42.png (109 KB) Snímek obrazovky 2022-02-22 v 13.35.42.png | Fail in webui |
Updated by okurz almost 3 years ago
- Category set to Regressions/Crashes
- Target version set to Ready
Updated by okurz almost 3 years ago
- Related to action #104970: Add two OSD workers (openqaworker14+openqaworker15) specifically for sap-application testing size:M added
Updated by livdywan almost 3 years ago
- Subject changed from [qe-tools] openqaworker14 and openqa15 - developer mode fails to [qe-tools] openqaworker14 and openqa15 - developer mode fails size:M
- Description updated (diff)
- Status changed from New to Workable
Updated by okurz almost 3 years ago
- Status changed from Workable to Blocked
- Assignee set to okurz
blocked by #104970
Updated by okurz over 2 years ago
- Status changed from Blocked to Workable
- Assignee deleted (
okurz)
Updated by okurz over 2 years ago
- Subject changed from [qe-tools] openqaworker14 and openqa15 - developer mode fails size:M to [qe-tools] openqaworker14 (and openqa15) - developer mode fails size:M
- Description updated (diff)
Updated by mkittler over 2 years ago
- Status changed from Workable to Resolved
The developer mode is working. I've checked several tests which are currently running on openqaworker14, e.g. https://openqa.suse.de/tests/8821312#live, https://openqa.suse.de/tests/8821350#live and https://openqa.suse.de/tests/8822624#live. Maybe it didn't work when you initially set those workers up but the problem has apparently been fixed in the meantime. (Maybe when I applied salt again in order to fix the MM setup.)
Note that openqaworker15 is not used on OSD anymore.