Bug 2233696
| Summary: | Logger does not capture data of a container after a container restart | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Carroline <cpippin> |
| Component: | podman-container | Assignee: | Jindrich Novy <jnovy> |
| Status: | CLOSED MIGRATED | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | medium | Docs Contact: | Michelle Bearer <mbearer> |
| Priority: | unspecified | ||
| Version: | 9.2 | Keywords: | MigratedToJIRA |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-11 20:31:16 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |
Description of problem: `logger test` from inside the container does not output the message after the container restarts Version-Release number of selected component (if applicable): RHEL 9.2 Podman How reproducible: Steps to Reproduce: 1. podman run -d --cap-add ALL --name logger registry.redhat.io/rhel9/rsyslog:latest 2. podman exec -it logger /bin/bash 3. Inside the Container : $ logger test 4. Outside the container: $ podman inspect --format='{{.HostConfig.LogConfig.Path}}' <container-id> 5. [root@rhel88 ~]# tail -f /var/lib/containers/storage/overlay-containers/4e1ceed92a9eaa8bb09196e825e1e1cbf4b1b8f6d60a6285c05d1532fb700ab9/userdata/ctr.log [root@4e1ceed92a9e /]# 2023-08-16T11:48:02.799138055+05:30 stdout P logger test 6. Stop and start the container and perform the same steps to capture logger output it does not log the message. Actual results: Logger does not log messages after a container restart Expected results: Logger should log messages always. Additional info: $ podman logs <container_id> does not log message after the restart as well.