Project

General

Profile

Actions

action #107497

closed

coordination #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

Added by osukup over 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2022-02-24
Due date:
% Done:

0%

Estimated time:
Tags:

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


Files


Related issues 1 (0 open1 closed)

Related to openQA Infrastructure - action #104970: Add two OSD workers (openqaworker14+openqaworker15) specifically for sap-application testing size:MResolvedmkittler2022-01-17

Actions
Actions

Also available in: Atom PDF