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.
Bug 2130912 - [RFE]Podman support to perform custom actions on unhealthy containers [rhel-8.6.0.z]
Summary: [RFE]Podman support to perform custom actions on unhealthy containers [rhel-8...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.6
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Alex Jia
URL:
Whiteboard:
Depends On: 2097708 2131741
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-29 12:13 UTC by RHEL Program Management Team
Modified: 2022-12-06 14:20 UTC (History)
18 users (show)

Fixed In Version: podman-4.1.1-7.el8
Doc Type: Enhancement
Doc Text:
.Podman now supports the `--health-on-failure` option With the release of the link:https://access.redhat.com/errata/RHBA-2022:7127[RHBA-2022:7127] advisory. the `podman run` and `podman create` commands now support the `--health-on-failure` option to determine the actions to be performed when the status of a container becomes unhealthy. The `--health-on-failure` option supports four actions: * `none`: Take no action, this is the default action. * `kill`: Kill the container. * `restart`: Restart the container. * `stop`: Stop the container. NOTE: Do not combine the `restart` action with the `--restart` option. When running inside of a systemd unit, consider using the `kill` or `stop` action instead to make use of systemd's restart policy.
Clone Of: 2097708
Environment:
Last Closed: 2022-10-25 09:33:30 UTC
Type: Enhancement
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers podman pull 15970 0 None Merged [v4.1.1-rhel] health check: add on-failure actions 2022-09-30 12:18:57 UTC
Red Hat Issue Tracker RHELBU-1919 0 None None None 2022-10-04 13:57:00 UTC
Red Hat Issue Tracker RHELPLAN-135297 0 None None None 2022-09-29 12:25:56 UTC
Red Hat Product Errata RHBA-2022:7127 0 None None None 2022-10-25 09:33:45 UTC

Comment 1 Tom Sweeney 2022-09-29 21:08:39 UTC 
Assigning to @jnovy for any further packaging or BZ needs.  Fix in Podman v4.1. branch at: https://github.com/containers/podman/pull/15961
Comment 7 Tom Sweeney 2022-10-11 17:58:57 UTC 
And as mentioned in email, Valentin has a fix for a related issue with the changes to the healthcheck.  That PR has just merged to the Podman v4.1.1-rhel branch at: https://github.com/containers/podman/pull/16115

Setting this BZ back to Post so that Jindrich can tie up any further packaging and BZ needs.
Comment 10 Alex Jia 2022-10-13 08:27:07 UTC 
This bug has been verified on podman-4.1.1-7.module+el8.6.0+16889+9f154fa9.x86_64.


[root@ibm-x3250m6-06 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.6 (Ootpa)

[root@ibm-x3250m6-06 ~]# rpm -q podman runc expat systemd kernel
podman-4.1.1-7.module+el8.6.0+16889+9f154fa9.x86_64
runc-1.1.3-2.module+el8.6.0+16771+28dfca77.x86_64
expat-2.2.5-8.el8_6.3.x86_64
systemd-239-58.el8_6.8.x86_64
kernel-4.18.0-372.32.1.el8_6.x86_64

[root@ibm-x3250m6-06 podman]# git branch
  main
* v4.1.1-rhel

[root@ibm-x3250m6-06 podman]# bats -t test/system/220-healthcheck.bats
1..2
ok 1 podman healthcheck
ok 2 podman healthcheck --health-on-failure

[root@ibm-x3250m6-06 podman]# bats -t -f "podman create --health-on-failure=kill" test/system/250-systemd.bats
1..1
ok 1 podman create --health-on-failure=kill
Comment 14 errata-xmlrpc 2022-10-25 09:33:30 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (container-tools:rhel8 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:7127
Note You need to log in before you can comment on or make changes to this bug.