-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Closed
Labels
flakesFlakes from Continuous IntegrationFlakes from Continuous Integrationlocked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.
Description
Two in the last week and a half. Both under vfs, which may be coincidence but I think it isn't Never mind, it's not a vfs thing:
<+073ms> # # podman logs 68fee835c41fcfbab5a673ec3457204394563e38857e979747d8ca457ef72608
<+086ms> # Error: error resolving symbol "sd_journal_open": libsystemd-journal.so.0: cannot open shared object file: No such file or directory
and:
# podman-remote [options] logs testPod-init-test
time="2023-11-02T06:49:37-05:00" level=error msg="Failed to get journal entry: failed to move journal cursor to next entry: error resolving symbol \"sd_journal_next\": libsystemd-journal.so.0: cannot open shared object file: No such file or directory"
Reminiscent of #17042, but different enough to merit its own issue. Also reminiscent of #20282.
- fedora-37 : sys podman fedora-37 rootless host boltdb
- PR e2e: more ExitCleanly() on more test files #19959
- 09-13-2023 10:39 in [sys] [email protected] template
- PR e2e: more ExitCleanly() on more test files #19959
- fedora-38 : int remote fedora-38 root host sqlite [remote]
- 11-02 08:02 in Podman kube play test with init containers and annotation set
- fedora-38 : sys podman fedora-38 root host sqlite
- 10-23 17:06 in [sys] podman networking: port with --userns=keep-id for rootless or --uidmap=* for rootful
Seen in: int+sys podman+remote fedora-37+fedora-38 root+rootless host sqlite
Metadata
Metadata
Assignees
Labels
flakesFlakes from Continuous IntegrationFlakes from Continuous Integrationlocked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.