action #93988


build openqa-review container within OBS with ca-certificates-suse package

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

Target version:
Start date:
Due date:
% Done:


Estimated time:



see #93710#note-12 . We build with certificates from but likely within IBS the package is not rebuilt on package updates. We have but that is missing CA repos. Instead we can now use so we should create a new project, e.g. a non-personal one (open for ideas where), with said repo enabled building openqa-review and use that in the project.

Acceptance criteria


  • Find a good new place for the container
  • Configure to use the CA repo in the container project
  • Verify that openqa-review in the newly built container can read from OSD
  • Update to use the new container
Actions #1

Updated by okurz over 2 years ago

container from works fine. Verified with

openqa-review -v --host

in the container running

podman run --rm -it


EDIT: Yes, that's "openqa-client" which is misnamed. Corrected :)

Actions #2

Updated by okurz over 2 years ago

  • Due date set to 2021-06-25
  • Status changed from In Progress to Feedback
Actions #3

Updated by jbaier_cz over 2 years ago

According to this job, python-openqa_review inside the container still does not know the parameter --skip-passed. There is an old version inside the container as can be seen from the:

$ zypper info $(zypper se -i openqa_review | grep ^i | cut -f2 -d\|)
Loading repository data...
Reading installed packages...
Information for package python38-openqa_review:
Repository     : openSUSE-Tumbleweed-Oss
Name           : python38-openqa_review
Version        : 1.21.0-1.1
Arch           : noarch
Vendor         : openSUSE
Installed Size : 266.8 KiB
Installed      : Yes
Status         : out-of-date (version 1.20.4-1.4 installed)
Source package : python-openqa_review-1.21.0-1.1.src
Summary        : A review helper script for openQA
Description    : 
    A review helper script for openQA. For more details look into the README file.

Apparently, although there is a newer version of the package, the container was not rebuild.

Actions #4

Updated by okurz over 2 years ago

Well, wasn't merged yet so this is why the container in the main pipeline does not have the new version yet. I have merged the MR now.

Actions #5

Updated by jbaier_cz over 2 years ago

I "backported" the patch into my fork as well to actually test the new container. But as we already clarified, the problem was solved by waiting longer. The container updates with a new Tumbleweed snapshot, not with a new package version in Factory.

Actions #6

Updated by okurz over 2 years ago

  • Status changed from Feedback to Resolved shows the correct container image being used.


Also available in: Atom PDF