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:

Is there any possibility to manage container state via systemd restart policy when it becomes "unhealthy", and has gracefully stopped?



Version-Release number of selected component (if applicable):
podman4.0.2-6 el8.6.0



How reproducible:

Use a command `podman generate systemd`, with parameter `--restart-policy` to generate a systemd container service.



Actual results:

If the relevant container systemd service will contain restart-policy set to "always", it allows restarting container again, after it is reaching unhealthy state.

If the testing container contains restart-policy "on-failure", podman API stops container with SIGTERM signal causing it to exit with 0 code - which corresponds to the normal behavior.




Expected results:

Killing "unhealthy" container, will cause it to terminate with not 0 exit code, but this approach may badly affect application state, which is running inside container.

Can container exit code be changed to something else?

Additional info:

I believe there may be some confusion here. Podman restart policy and healthchecks at present are entirely unconnected. You say that the `on-failure` restart policy will kill containers in an unhealthy state, but this is incorrect; Podman restart policy will never kill a container.

This sounds like it could be reworded as an RFE for a new restart policy, though. Is the request to restart containers that are unhealthy, or to not restart containers that are unhealthy and exited, or both?

I am verifying, but I believe this is addressed with https://github.com/containers/podman/pull/15687 from @vrothber Correct Valentin?

(In reply to Tom Sweeney from comment #10)
> I am verifying, but I believe this is addressed with
> https://github.com/containers/podman/pull/15687 from @vrothber
> Correct Valentin?

Yes, this BZ and https://bugzilla.redhat.com/show_bug.cgi?id=2097708 are effectively the same request.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days