Project

General

Profile

action #80534

coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes

coordination #43706: [epic] Generate "download&use" docker image of openQA for SUSE QA

publication+demo for updated openQA containers

Added by okurz over 2 years ago. Updated almost 2 years ago.

Status:
Blocked
Priority:
Normal
Assignee:
okurz
Category:
Feature requests
Target version:
QA - future
Start date:
2020-11-27
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:
container, announcement, publication

Description

Motivation

Given that we have updated our container definitions for openQA webUI+worker and publish them as part of our OBS project we should make sure that people know about these containers.

Acceptance criteria

  • AC1: An announcement for the updated openQA containers has been provided
  • AC2: A demo exists and is presented as part of the announcement

Suggestions

Further details

Please do not phrase it as "Finally we have containers" or something because we had them for years but we improved the experience and ensure to provide recurringly updated versions

History

#1 Updated by okurz over 2 years ago

  • Tracker changed from coordination to action

#2 Updated by ilausuch over 2 years ago

  • Status changed from Workable to In Progress

#3 Updated by ilausuch over 2 years ago

  • Assignee set to ilausuch

#4 Updated by ilausuch over 2 years ago

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

#5 Updated by okurz over 2 years ago

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?

#6 Updated by openqa_review over 2 years ago

  • Due date set to 2020-12-17

Setting due date based on mean cycle time of SUSE QE Tools

#7 Updated by okurz over 2 years ago

  • Due date deleted (2020-12-17)
  • Status changed from In Progress to Blocked
  • Target version changed from Ready to future

as discussed in daily-extension 2020-12-03 and as ilausuch suggested we should block this ticket by #80520 and #80682 hence also removing due-date and setting to "future".

#8 Updated by ilausuch over 2 years ago

The ticket #88187 blocks this ticket

#9 Updated by ilausuch almost 2 years ago

  • Assignee deleted (ilausuch)

#10 Updated by okurz almost 2 years ago

  • Assignee set to okurz

Also available in: Atom PDF