action #130141
closedtest fails in podman_netavark on SLEM on Azure
100%
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
Updated by ph03nix over 1 year ago
- Related to action #124631: Usage of netavark and aardvark in podman networks added
Updated by ph03nix over 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.
Updated by ph03nix over 1 year ago
Re-establishing the user console doesn't work: https://duck-norris.qe.suse.de/tests/12927#step/podman_netavark/89
Updated by ph03nix over 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.
Updated by ph03nix over 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
Updated by jlausuch over 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 inslem_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?
Updated by ph03nix over 1 year ago
- File nobernhard.png nobernhard.png added
For some reason in the failing step the user bernhard
does not exist anymore. The ssh config assumes the user to be present.
Updated by ph03nix over 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.
Updated by ph03nix over 1 year ago
- File dödelmeier1.png dödelmeier1.png added
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.
Updated by ph03nix over 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
Updated by jlausuch over 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...
Updated by ph03nix over 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.
Updated by ph03nix over 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.
Updated by ph03nix over 1 year ago
- % Done changed from 0 to 70
Updated by ph03nix over 1 year ago
Updated by ph03nix over 1 year ago
- Status changed from In Progress to Resolved
- % Done changed from 70 to 100
Fixed.