action #76771: [qac][containers] Support containers tests on openSUSE - Containers and images - openSUSE Project Management Tool

Actions

Copy link

action #76771

closed

coordination #66535: [qac][containers][epic] Provide advanced testing coverage for SLE base container

[qac][containers] Support containers tests on openSUSE

Added by jlausuch about 4 years ago. Updated almost 4 years ago.

Status:

Resolved

Priority:

High

Assignee:

ybonatakis

Target version:

Start date:

2020-10-29

Due date:

% Done:

Estimated time:

Tags:

qac, containers

Description

SLE base container shall be supported on openSUSE Leap and optionally Tumbleweed.

Update:
Just to clarify, this task is NOT about building SLE container on SLE or openSUSE. This is only about testing that the base container image call be pulled on openSUSE the same way we do for CentOS and Ubuntu.

Later on we will talk about advanced test cases like building SLE image on SLE host and porting it to 3rd party platforms.

Hide closed

Checklist

Leap 15.1
Leap 15.2

Actions

Copy link

Updated by jlausuch about 4 years ago

Parent task set to #66535

Actions

Copy link

Updated by ybonatakis about 4 years ago

Status changed from Workable to In Progress
Assignee set to ybonatakis

Actions

Copy link

Updated by jlausuch about 4 years ago

Project changed from openQA Tests to Containers and images
Category deleted (~~New test~~)

Actions

Copy link

Updated by ybonatakis about 4 years ago

Project changed from Containers and images to openQA Tests

According to Vogt is "What's supported and should be tested is that containers built on SLE also run on openSUSE, but it's not supported to build SLE images on openSUSE".
So am i going to build an image and push it in the o3.

@jlausuch any objections?

Actions

Copy link

Updated by jlausuch about 4 years ago

I wouldn't go to O3. Let's reduce the scope to basically the same smoke test as we do for CentOS and Ubuntu (podman_image, docker_image tests)

Let's use a pre-installed openSUSE image for this and put it in fixed directory of OSD NFS share. In fact, there is something already existing:

jlausuch@openqa:/var/lib/openqa/share/factory/hdd/fixed> ll|grep -i opensuse
-rw-r--r-- 1 leli      users    2571108352 Jun 26 14:05 opensuse-15.2-x86_64-GM-gnome@64bit.qcow2
-rw-r--r-- 1 leli      users    1026818048 Jun 26 11:34 opensuse-15.2-x86_64-GM-textmode@64bit.qcow2

Actions

Copy link

Updated by okurz about 4 years ago

jlausuch wrote:

I wouldn't go to O3. Let's reduce the scope to basically the same smoke test as we do for CentOS and Ubuntu (podman_image, docker_image tests)

Not sure what you mean with "I wouldn't go to O3": I recommend to test as much as possible in openSUSE because then you get the support of the community and earlier feedback and also follow the https://opensource.suse.com/suse-open-source-policy.html

Let's use a pre-installed openSUSE image for this and put it in fixed directory of OSD NFS share

Just to clarify: Maybe you. The "NFS share" should be avoided and should not be relied upon as not all workers can support it and we already did fade it out once.

Actions

Copy link

Updated by jlausuch about 4 years ago

Description updated (diff)

Actions

Copy link

Updated by jlausuch about 4 years ago

Not sure what you mean with "I wouldn't go to O3": I recommend to test as much as possible in openSUSE because then you get the support of the community and earlier feedback and also follow the https://opensource.suse.com/suse-open-source-policy.html

O3 is not a place to test SLE images. That's why.

Actions

Copy link

Updated by okurz about 4 years ago

jlausuch wrote:

O3 is not a place to test SLE images. That's why.

Hm, maybe it's still a good place, e.g. there is also https://registry.suse.com/ which is public

SLE 15-SP3 image is not there yet, we get it from internal registry, concretely:
registry.suse.de/suse/sle-15-sp3/update/cr/totest/images/suse/sle15:15.3

Actions

Copy link

#10