Bug 1218023

Summary: [Build 44.1] openQA test fails in rootless_podman
Product: [openSUSE] PUBLIC SUSE Linux Enterprise Server 15 SP6 Reporter: Pablo Herranz Ramírez <pablo.herranz>
Component: ContainersAssignee: Containers Team <containers-bugowner>
Status: RESOLVED INVALID QA Contact:
Severity: Normal    
Priority: P1 - Urgent CC: dcermak, pdostal, rtsvetkov
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://openqa.suse.de/tests/13060038/modules/rootless_podman/steps/110
Whiteboard:
Found By: openQA Services Priority:
Business Priority: Blocker: Yes
Marketing QA Status: --- IT Deployment: ---

Description Pablo Herranz Ramírez 2023-12-13 13:37:19 UTC 
## Observation

openQA test in scenario sle-15-SP6-Online-x86_64-podman_cgroup_v1_tests@64bit fails in
[rootless_podman](https://openqa.suse.de/tests/13060038/modules/rootless_podman/steps/110)

## 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 [44.1](https://openqa.suse.de/tests/13048896)


## Expected result

Last good: (unknown) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=podman_cgroup_v1_tests&version=15-SP6)


In rootless podman I cannot obtain the logs from a container as normal user:

```
> podman create --name testing registry.opensuse.org/opensuse/tumbleweed:latest /bin/sh -c '/bin/uname -r; /bin/echo Heartbeat'
> podman container start testing
> podman wait testing
> podman container logs testing
(empty)
```

However it works as root:

```
# podman create --name testing registry.opensuse.org/opensuse/tumbleweed:latest /bin/sh -c '/bin/uname -r; /bin/echo Heartbeat'
# podman container start testing
# podman wait testing
# podman container logs testing
6.4.0-150600.4-default
Heartbeat
```
Comment 1 Dan Čermák 2023-12-13 14:38:17 UTC 
This is caused by the unprivileged user not having privileges to read journald. You can either add the user to the systemd-journal group:

usermod -a -G systemd-journal bernhard

or follow this guide:
https://documentation.suse.com/sles/15-SP4/html/SLES-all/cha-journalctl.html#sec-journalctl-persistent