QA » openQA Project

I found this problem running directly with podman the web UI

$ podman run --rm -it registry.opensuse.org/devel/openqa/containers15.2/openqa_webui:latest
AH00526: Syntax error on line 18 of /etc/apache2/vhosts.d/openqa-ssl.conf:
SSLCertificateFile: file '/etc/apache2/ssl.crt/server.crt' does not exist or is empty

Yes, we have discussed the problem already when you were working on the Dockerfiles. perl-Mojolicous has crt+key files we can use, e.g. try:

podman run --rm -it -v /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/resources/server.crt:/etc/apache2/ssl.crt/server.crt -v /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/resources/server.key:/etc/apache2/ssl.key/server.key -v /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/resources/server.crt:/etc/apache2/ssl.crt/ca.crt registry.opensuse.org/devel/openqa/containers15.2/openqa_webui:latest

However this does not bring me far either, output:

AH00558: httpd-prefork: Could not reliably determine the server's fully qualified domain name, using 10.88.0.53. Set the 'ServerName' directive globally to suppress this message
[2020-12-02 14:28:05.45534] [9] [warn] No configuration file supplied, will fallback to default configuration
[2020-12-02 14:28:05.45735] [10] [warn] No configuration file supplied, will fallback to default configuration
Usage: APPLICATION COMMAND [OPTIONS]
…
See 'APPLICATION help COMMAND' for more information on a specific command.
[2020-12-02 14:28:05.74566] [23] [warn] No configuration file supplied, will fallback to default configuration
Can not create MOJO_TMPDIR : mkdir /var/lib/openqa/share/factory: File exists at /usr/share/openqa/script/../lib/OpenQA/Setup.pm line 288.

Failed to open /usr/share/openqa/script/../etc/openqa/database.ini: No such file or directory at /usr/share/openqa/script/../lib/OpenQA/Schema.pm line 56.
Could not find database section 'production' in /usr/share/openqa/script/../etc/openqa/database.ini at /usr/share/openqa/script/../lib/OpenQA/Schema.pm line 57.
[2020-12-02 14:28:05.75702] [8] [warn] No configuration file supplied, will fallback to default configuration

well, this is clearly something out of scope for "publication+demo". So it seems the former story is not really finished. Should we reopen #43712 or do you prefer that we work on #80520 first?

The ticket #88187 blocks this ticket