QA » openQA Project » openQA Tests » Containers

@ph03nix can you please get rid of rancher::kubectl_basic_test and create your new subroutines in containers::k8s instead?

After discovering https://bugzilla.opensuse.org/show_bug.cgi?id=1200876 and realizing that kubeadm is broken on Tumbleweed due to outdated images:

failed to pull image "registry.opensuse.org/kubic/pause:3.7": output: E0623 14:37:13.894254   19657 remote_image.go:238] "PullImage from image service failed" err="rpc error: code = Unknown desc = reading manifest 3.7 in registry.opensuse.org/kubic/pause: manifest unknown" image="registry.opensuse.org/kubic/pause:3.7"
time="2022-06-23T14:37:13+02:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = reading manifest 3.7 in registry.opensuse.org/kubic/pause: manifest unknown"
, error: exit status 1
To see the stack trace of this error execute with --v=5 or higher

I realize it might be a good idea to follow our Factory first principle and start to establish some tests for Tumbleweed as a first step.

ph03nix wrote:

After discovering https://bugzilla.opensuse.org/show_bug.cgi?id=1200876 and realizing that kubeadm is broken on Tumbleweed due to outdated images:

failed to pull image "registry.opensuse.org/kubic/pause:3.7": output: E0623 14:37:13.894254   19657 remote_image.go:238] "PullImage from image service failed" err="rpc error: code = Unknown desc = reading manifest 3.7 in registry.opensuse.org/kubic/pause: manifest unknown" image="registry.opensuse.org/kubic/pause:3.7"
time="2022-06-23T14:37:13+02:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = reading manifest 3.7 in registry.opensuse.org/kubic/pause: manifest unknown"
, error: exit status 1
To see the stack trace of this error execute with --v=5 or higher

I realize it might be a good idea to follow our Factory first principle and start to establish some tests for Tumbleweed as a first step.
+1

I find this approach good.

I just did not expect that Felix will pick kubeadm on Tumbleweed when we have for example EKS :smile:

But again, I find this approach very cool.

https://build.opensuse.org/request/show/984715 Is for the updated kubic/pause image. Need to wait until it becomes available.

I was fiddling around with kubeadm for the whole morning and I'm making slow progress. Will still try a bit, but I'm considering to just use k3s as a kubernetes platform where we run kubectl against. Setup is easy and it provides the API that we need in order to test the kubectl package.

This issue will have to wait a bit, since https://progress.opensuse.org/issues/112400 is more important now.

New PR to start fresh after a lot of changes: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15215

I've added the containers_host_kubectl test run on O3 in Tumbleweed/Development:

    - containers_host_kubectl:
        testsuite: extra_tests_textmode_containers
        settings:
          CONTAINER_RUNTIME: 'kubectl'

Let's wait for tomorrow's test runs.

ph03nix wrote:

I've added the containers_host_kubectl test run on O3 in Tumbleweed/Development:

    - containers_host_kubectl:
        testsuite: extra_tests_textmode_containers
        settings:
          CONTAINER_RUNTIME: 'kubectl'

Let's wait for tomorrow's test runs.

Nice! After a few green runs, it can be moved to main group.

Let's not get overly optimistic, I'm pretty sure somewhere I screwed up and it will take still 1-2 iterations until it actually lands ;-)

HOLY MOLY, it works! https://openqa.opensuse.org/tests/2473469

Let's wait for another 1-2 days and then move it to the main Tumbleweed test runs.

Huh? For some reason there is no kubectl test run in the Development group today. It is still present in the job groups though.

ph03nix wrote:

Huh? For some reason there is no kubectl test run in the Development group today. It is still present in the job groups though.

I see it https://openqa.opensuse.org/tests/2475514

Huh? For some reason there is no kubectl test run in the Development group today. It is still present in the job groups though.

jlausuch wrote:

ph03nix wrote:

Huh? For some reason there is no kubectl test run in the Development group today. It is still present in the job groups though.

I see it https://openqa.opensuse.org/tests/2475514

Looks like they are being scheduled later on the day. Anyways, two successful test runs, I think I'm gonna push this to the main Tumbleweed group today.

https://github.com/os-autoinst/opensuse-jobgroups/pull/177

I also added the test run to Development/Tumbleweed aarch64

ph03nix wrote:

Job groups scheduled for Tumbleweed. Will mark the ticket as resolved when tomorrow's test runs are being scheduled correctly.

Since there has not been an new build and you are leaving on FTO, I'll take care!