Project

General

Profile

action #92893

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

Added by ilausuch 2 months ago. Updated 9 days ago.

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

0%

Estimated time:
Difficulty:

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

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

Blocks openQA Project - action #76978: How to run an openQA test in 5 minutesBlocked2020-11-04

History

#1 Updated by ilausuch 2 months ago

  • Related to action #92833: containers: Web UI cannot connect to scheduler added

#2 Updated by ilausuch 2 months ago

  • Blocks action #76978: How to run an openQA test in 5 minutes added

#3 Updated by ilausuch 2 months ago

  • Description updated (diff)

#4 Updated by VANASTASIADIS 2 months ago

  • Target version set to future

#5 Updated by okurz 30 days ago

  • Subject changed from containers: the scheduler cannot connect to the websockets container to containers, docker-compose: the scheduler cannot connect to the websockets container
  • Category changed from Concrete Bugs to Feature requests
  • Target version changed from future to Ready

Changing to "Feature requests" as this never worked so not a regression.

#6 Updated by ilausuch 13 days ago

  • Subject changed from containers, docker-compose: the scheduler cannot connect to the websockets container to containers, docker-compose: Ensure that the scheduler can connect to the websockets container
  • Description updated (diff)

#7 Updated by okurz 9 days ago

  • Priority changed from Normal to Low

#8 Updated by ilausuch 9 days ago

Last week appeared this ticket in our meetings and I had an idea to check that I don't wanted to forget

In the scheduler container we don't have the client.ini with the credentials. This could be a clue to follow

4adc570f1117:/data/conf # ls
database.ini openqa.ini

Also available in: Atom PDF