Project

General

Profile

Actions

action #130141

closed

test fails in podman_netavark on SLEM on Azure

Added by ph03nix about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Target version:
-
Start date:
2023-05-31
Due date:
% Done:

100%

Estimated time:
Tags:

Description

Observation

openQA test in scenario sle-micro-5.4-BYOS-Azure-x86_64-slem_containers@64bit fails in
podman_netavark

openQA test in scenario sle-micro-5.4-BYOS-Azure-ARM-x86_64-slem_containers@64bit fails in
podman_netavark

The issue is present on Azure and Azure-ARM, but not on GCE or AWS.

Test suite description

The base test suite is used for job templates defined in YAML documents. It has no settings of its own.

Reproducible

Fails since (at least) Build 0114 (current job)

Expected result

Last good: 0113 (or more recent)

Further details

Always latest result in this scenario: latest


Files

nobernhard.png (86.9 KB) nobernhard.png ph03nix, 2023-06-01 14:32
dödelmeier1.png (87.6 KB) dödelmeier1.png ph03nix, 2023-06-01 14:54

Related issues 1 (0 open1 closed)

Related to Containers - action #124631: Usage of netavark and aardvark in podman networksResolvedmloviska2023-02-15

Actions
Actions #1

Updated by ph03nix about 1 year ago

  • Related to action #124631: Usage of netavark and aardvark in podman networks added
Actions #2

Updated by ph03nix about 1 year ago

  • Description updated (diff)
Actions #3

Updated by ph03nix about 1 year ago

https://openqa.suse.de/tests/11210668#step/podman_netavark/82 looks like an issue with establishing the ssh tunnel (password required) but I'm not sure.

I could not reproduce any issues with a test instance after installing netavark and aardvark-dns in one transaction:

zoidberg:~ # transactional-update pkg install netavark aardvark-dns
...

Please reboot your machine to activate the changes and avoid data loss.
New default snapshot is #4 (/.snapshots/4/snapshot).
transactional-update finished

zoidberg:~ # reboot

Instance works just as expected.

Actions #4

Updated by ph03nix about 1 year ago

Re-establishing the user console doesn't work: https://duck-norris.qe.suse.de/tests/12927#step/podman_netavark/89

Actions #5

Updated by ph03nix about 1 year ago

But it works in the previous step: https://duck-norris.qe.suse.de/tests/12927#step/slem_prepare/45

Also, I could not reproduce the issue on a fresh SLEM 5.4 instance on Azure using the system defaults. Gonna check, what could be the difference and then proceed from there.

Actions #6

Updated by ph03nix about 1 year ago

The issue is that connecting via the default user bernhard fails in https://duck-norris.qe.suse.de/tests/12929#step/podman_netavark/97 after preparing podman netavark. This step works previously in slem_prepare: https://duck-norris.qe.suse.de/tests/12929#step/slem_prepare/48

Actions #7

Updated by jlausuch about 1 year ago

ph03nix wrote:

The issue is that connecting via the default user bernhard fails in https://duck-norris.qe.suse.de/tests/12929#step/podman_netavark/97 after preparing podman netavark. This step works previously in slem_prepare: https://duck-norris.qe.suse.de/tests/12929#step/slem_prepare/48

ah I should have figured before... cause we don't have bernhard created by default in PC images, right?

Actions #8

Updated by ph03nix about 1 year ago

For some reason in the failing step the user bernhard does not exist anymore. The ssh config assumes the user to be present.

Actions #9

Updated by ph03nix about 1 year ago

jlausuch wrote:

ah I should have figured before... cause we don't have bernhard created by default in PC images, right?

bernhard is being created and is being used, see https://duck-norris.qe.suse.de/tests/12929#step/slem_prepare/48, that's why this is so puzzling.

Actions #10

Updated by ph03nix about 1 year ago

This is weird. The user bernhard is created and exists after the slem_prepare step:

Compare this to the screenshot of podman-netavark, where bernhard does not exist anymore:

There is something fishy going on here.

Actions #11

Updated by ph03nix about 1 year ago

Rebooting somehow removes the bernhard user after the toolbox test: https://duck-norris.qe.suse.de/tests/12935#step/reboot#1/58

Actions #12

Updated by jlausuch about 1 year ago

ph03nix wrote:

Rebooting somehow removes the bernhard user after the toolbox test: https://duck-norris.qe.suse.de/tests/12935#step/reboot#1/58

Azure and its own peculiarities... what a surprise...

Actions #13

Updated by ph03nix about 1 year ago

jlausuch wrote:

Azure and its own peculiarities... what a surprise...

I smell something fishy here, but will need some time to investigate. Today with all the meetings it's impossible.

Actions #14

Updated by ph03nix about 1 year ago

The problem is that toolbox removes the testapi user bernhard after running, even if other tests (e.g. PC test runs) still need it. This is a test issue.

Actions #17

Updated by ph03nix about 1 year ago

  • Status changed from In Progress to Resolved
  • % Done changed from 70 to 100

Fixed.

Actions

Also available in: Atom PDF