Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
A container with `--healthcheck-interval` and `--healthcheck-timeout` options able to restart but with an error.
Version-Release number of selected component (if applicable):
RHEL - 8.5
Podman - 3.3.1
How reproducible:
100% reproducible
Steps to Reproduce:
1. Run the container with `--healthcheck-interval` and `--healthcheck-timeout` options
$ podman run -dit --name test --health-cmd="/bin/foobar" --healthcheck-interval=15s --health-timeout=10s ubi8
4b3b5a710eb963708e8ee808604f997ab557b88d25499495061d8c360063b43f
2. Check the files created under /run/systemd/transient/
$ ls -l /run/systemd/transient/ | grep 4b3b5a710eb963708e8ee808604f997ab557b88d25499495061d8c360063b43f
-rw-r--r--. 1 root root 441 Jan 20 10:06 4b3b5a710eb963708e8ee808604f997ab557b88d25499495061d8c360063b43f.service
-rw-r--r--. 1 root root 275 Jan 20 10:06 4b3b5a710eb963708e8ee808604f997ab557b88d25499495061d8c360063b43f.timer
-rw-r--r--. 1 root root 348 Jan 20 10:06 libpod-4b3b5a710eb963708e8ee808604f997ab557b88d25499495061d8c360063b43f.scope
drwxr-xr-x. 2 root root 100 Jan 20 10:06 libpod-4b3b5a710eb963708e8ee808604f997ab557b88d25499495061d8c360063b43f.scope.d
-rw-r--r--. 1 root root 164 Jan 20 10:06 libpod-conmon-4b3b5a710eb963708e8ee808604f997ab557b88d25499495061d8c360063b43f.scope
3. Restart the container and see it starts but throws an error.
$ podman restart test
ERRO[0001] Failed to start transient timer unit: Unit 4b3b5a710eb963708e8ee808604f997ab557b88d25499495061d8c360063b43f.timer already exists.
4b3b5a710eb963708e8ee808604f997ab557b88d25499495061d8c360063b43f
$ podman ps | grep test2
4b3b5a710eb9 registry.access.redhat.com/ubi8:latest /bin/bash 51 seconds ago Up 17 seconds ago test
Actual results:
The container able to restart but with an error.
$ podman restart test
ERRO[0001] Failed to start transient timer unit: Unit 4b3b5a710eb963708e8ee808604f997ab557b88d25499495061d8c360063b43f.timer already exists.
4b3b5a710eb963708e8ee808604f997ab557b88d25499495061d8c360063b43f
Expected results:
The container should be able to restart cleanly without an error
Additional info: