action #64290: Docker container "openqa_webui" throws an exception when trying to run. - openQA Project (public) - openSUSE Project Management Tool

Actions

Copy link

action #64290

closed

Docker container "openqa_webui" throws an exception when trying to run.

Added by DaNizz97 almost 5 years ago. Updated over 4 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

okurz

Category:

Support

Target version:

QA (public) - future

Start date:

2020-03-07

Due date:

2020-08-05

% Done:

Estimated time:

Description

The exception is:
Uncaught exception from user code: DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect('dbname=openqa','',...) failed: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? at /usr/lib/perl5/vendor_perl/5.18.2/DBIx/Class/Storage/DBI.pm line 1517. at /usr/lib/perl5/vendor_perl/5.18.2/x86_64-linux-thread-multi/Moose/Meta/Method/Delegation.pm line 110

The command to run the container:
docker run -d --privileged -h opqa_webui --name opqa_webui --volumes-from opqa_data -p 8088:80 -p 4433:443 openqa/webui

Files

Download all files

SeaBIOS_Stuck.png (18.1 KB) SeaBIOS_Stuck.png		DaNizz97, 2020-03-18 13:25
worker-log.txt (1.28 KB) worker-log.txt		DaNizz97, 2020-03-18 13:28
vars.json (1.22 KB) vars.json		DaNizz97, 2020-03-18 13:28
autoinst-log.txt (23.9 KB) autoinst-log.txt		DaNizz97, 2020-03-18 13:28

Actions

Copy link

Updated by DaNizz97 almost 5 years ago

The same error occurs when trying to build and run the image with https://github.com/os-autoinst/openQA/blob/master/docker/webui/Dockerfile

Actions

Copy link

Updated by okurz almost 5 years ago

Hi DaNizz97, thanks for the report. Unfortunately the container "openqa_webui" is not periodically tested and a bit "rough around the edges" ;) The better supported and suggested ways for installing and deploying an openQA installation are described in http://open.qa/docs/#installing . However, if you still want to continue with the docker containers – no guarantees given – let me try to explain to you what the error means: The openQA-webui needs a postgres database which is not automatically provided by the container itself. You might be able to install a postgres server when you build the docker images yourself from the current state in the github project. The images on docker hub are unfortunately very old and based on end-of-life openSUSE Leap 42.2 where I don't see it feasible to use them easily. One can of course replace repositories within the image with a current openSUSE Leap 15.1 and upgrade to that version but building updated images is probably easier for you :)

Actions

Copy link Download all files

Updated by DaNizz97 almost 5 years ago

File SeaBIOS_Stuck.png SeaBIOS_Stuck.png added
File vars.json vars.json added
File worker-log.txt worker-log.txt added
File autoinst-log.txt autoinst-log.txt added

Hello okurz. Thanks for the answer. I've fixed the issue with the database connection, but unfortunately, I've met another problem - probably with qemu/kvm. When I'm running a job, it looks like my iso file is not booted - 'Live View' is stucks on the black screen with "SeaBIOS (version ?-20190727...)" text (see attachments).
Actually, when I started openQA on my local Fedora without docker with the same iso and configurations(Medium types, Machines and other), I did not encounter such an error.
autoinst-log.txt files are equivalent in both cases: when I use docker and when I use local Fedora (which is running well).
I also changed the HOST and WORKER_HOST values in workers.ini, but this had no effect.

Could you please help or give advise, how can I debug this issue. I understand that it is better to use the openQA as is, without docker, but I have no such opportunity :(

Actions

Copy link

Updated by mkittler almost 5 years ago

Apparently QEMU can be started but it does not what's expected. The qemu command line is present in the log file you've attached. You can try to run it manually within the container and play around with the parameters. (You can start the worker with --no-cleanup to prevent it from deleting files from the pool directory.)

Actions

Copy link