action #80682: Automatic tests for our openQA containers - worker only - openQA Project - openSUSE Project Management Tool

action #80682

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

Automatic tests for our openQA containers - worker only

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

Status:

Resolved

Priority:

Normal

Assignee:

ilausuch

Category:

Feature requests

Target version:

Ready

Start date:

2020-11-27

Due date:

% Done:

Estimated time:

Difficulty:

Description

Motivation¶

Without automatic tests we would not call any contributions properly long-term supportable. These tests could be very simple, e.g. something like podman run --rm -it .... openqa-worker --help or something.

Acceptance criteria¶

AC2: The worker service(s) is/are started completely without errors from container within CI tests, i.e. stops asking for webUI server to connect to

Suggestions¶

Find out if OBS can execute tests for container images
Consider kiwi vs Dockerfile
Setup tests as part of the openQA CI (e.g. CircleCI or GitHub Actions)

Related issues

History

#1 Updated by okurz over 2 years ago

Copied from action #80520: Automatic tests for our openQA containers - webUI only added

#2 Updated by okurz over 2 years ago

Copied to action #80684: Automatic tests for our openQA containers - worker+webui connection added

#3 Updated by ilausuch over 2 years ago

Status changed from Workable to In Progress
Assignee set to ilausuch

#4 Updated by openqa_review over 2 years ago

Due date set to 2020-12-19

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

#5 Updated by ilausuch over 2 years ago

First PR iniciative
~~https://github.com/os-autoinst/openQA/pull/3623~~
https://github.com/os-autoinst/openQA/pull/3634

#6 Updated by cdywan over 2 years ago

Status changed from In Progress to Feedback

This has been discussed a bit to see what the best way forward is. #81118 is about testing for os-autoinst and currently proposes a PR using GitHub Actions.

It was also suggested to extend our openqa in openqa tests, where already test the scenarios of installing openQA from git and from packages respectively

#7 Updated by cdywan over 2 years ago

Due date deleted (~~2020-12-19~~)

ilausuch Please mention the result of trying the openQA test approach herelater. For now I'm resetting the due date due to holidays.

#8 Updated by ilausuch over 2 years ago

Status changed from Feedback to In Progress

#9 Updated by openqa_review over 2 years ago

Due date set to 2021-02-09

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

#10 Updated by ilausuch over 2 years ago

The current test (https://openqa.opensuse.org/tests/1607448) works:

Cannot finally connect to the webUI because doesn't have the credentials. Obtaining a key/secret is not trivial, so this test cannot continue until we have this feature.

#11 Updated by cdywan over 2 years ago

ilausuch wrote:

The current test (https://openqa.opensuse.org/tests/1607448) works:

Cannot finally connect to the webUI because doesn't have the credentials. Obtaining a key/secret is not trivial, so this test cannot continue until we have this feature.

Would you mind filing a new ticket for the missing feature to create users with credentials? I'd consider it out of scope for this ticket.

#12 Updated by ilausuch over 2 years ago

Done. The new ticket is https://progress.opensuse.org/issues/88315

#13 Updated by okurz over 2 years ago

Our ACs as defined in this ticket already correctly describe what is needed and that does not include the "proper connection", just trying to start and failing as expected.