Project

General

Profile

Actions

action #92893

closed

containers, docker-compose: Ensure that the scheduler can connect to the websockets container size:M

Added by ilausuch almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2021-05-20
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Trying to complete the task #76978 I found a problem in the webui container. It cannot connect to the scheduler and the jobs still unscheduled

scheduler_1      | -- Blocking request (http://127.0.0.1:9527/api/send_job)
scheduler_1      | -- Connect 41d600104970be636ece6296a21d1bdc (http://127.0.0.1:9527)

It could be easily fixed adding OPENQA_WEB_SOCKETS_HOST: "websockets" to the scheduler declaration

But then an other problems happens:

scheduler_1      | -- Client <<< Server (http://websockets:9527/api/send_job)
scheduler_1      | HTTP/1.1 403 Forbidden\x0d
scheduler_1      | Content-Length: 26\x0d
scheduler_1      | Server: Mojolicious (Perl)\x0d
scheduler_1      | Date: Thu, 20 May 2021 10:24:45 GMT\x0d
scheduler_1      | Content-Type: application/json;charset=UTF-8\x0d
scheduler_1      | \x0d
scheduler_1      | {"error":"Not authorized"}

This happens when we launch a web UI openQA using the docker-compose, and try to run a job (using clone_job)

Acceptance Criteria

  • AC 1: scheduler can connect to websockets without problems

Suggestions

  • Investigate the auth method to these services. Maybe the auth method is only localhost
  • Check that the client.ini has the correct credentials

References

See the comments at #92833#note-6


Related issues 3 (1 open2 closed)

Related to openQA Project - action #92833: containers: Web UI cannot connect to schedulerResolvedilausuch2021-05-192021-06-04

Actions
Related to openQA Project - coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetesBlockedokurz2018-09-26

Actions
Blocks openQA Project - action #76978: How to run an openQA test in 5 minutes size:MResolvedjbaier_cz2020-11-04

Actions
Actions

Also available in: Atom PDF