action #104571
closed[qe-core]test fails in rootless_podman on RPi3 (and RPi4)
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-JeOS-for-RPi-aarch64-jeos-containers@RPi3 fails in
rootless_podman
The test fails in rootless_podman on RPi3 (and RPi4), but it succeeds in qemu, see: https://openqa.opensuse.org/tests/2119543
Test suite description¶
JeOS as container host. Test container runtimes (podman and docker) and related tools.
@jlausuch (2021-11-25): I have removed BOOT_HDD_IMAGE=1, since it's irrelevant for JeOS and schedules unwanted modules in main_containers.pm
Reproducible¶
Fails since (at least) Build 20211202
Expected result¶
Last good: 20211130 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by maritawerner over 2 years ago
- Subject changed from test fails in rootless_podman on RPi3 (and RPi4) to [qe-core]test fails in rootless_podman on RPi3 (and RPi4)
- Assignee set to dheidler
Dominik, I think that is for you?
Updated by dheidler over 2 years ago
- Status changed from In Progress to Feedback
I think this is a product bug - so let's see what comes from
https://bugzilla.suse.com/show_bug.cgi?id=1194645
I was able to reproduce this on rpi4 hardware.
Updated by dheidler over 2 years ago
- Status changed from Feedback to In Progress
This might be not a product bug but related to the login mechanism that is used:
On qemu systems we login via tty in this this module (https://openqa.opensuse.org/tests/2119543#step/rootless_podman/51) but on the raspberry pi we only have serial and ssh - so we ssh to the system as root and then call su - bernhard (https://openqa.opensuse.org/tests/2133066#step/rootless_podman/53) which doesn't initiate a logind session.
So running loginctl enable-linger 1000 as root before doing the podman build could be a workaround.
Updated by dheidler over 2 years ago
- Status changed from In Progress to Feedback
Updated by dheidler about 2 years ago
- Status changed from Feedback to Resolved