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.

Bug 2149775

Summary: FailingStreak is not reset to 0 when the container starts again. [rhel-8.7.0.z]
Product: Red Hat Enterprise Linux 8 Reporter: RHEL Program Management Team <pgm-rhel-tools>
Component: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED ERRATA QA Contact: Alex Jia <ajia>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: ---CC: ajia, bbaude, dornelas, dwalsh, jligon, jnovy, lsm5, mheon, pthomas, rjo, snanda, tsweeney, umohnani, vrothber, ypu
Target Milestone: rcKeywords: Triaged, ZStream
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: podman-4.2.0-5.el8_7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2144754 Environment:
Last Closed: 2023-01-12 09:24:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2144754    
Bug Blocks:    

Comment 6 Alex Jia 2022-12-14 07:35:34 UTC 
This bug has been verified on podman-4.2.0-5.module+el8.7.0+17435+870a78db.x86_64.

[root@ibm-x3650m4-01-vm-05 podman]# rpm -q podman runc systemd kernel
podman-4.2.0-5.module+el8.7.0+17435+870a78db.x86_64
runc-1.1.4-1.module+el8.7.0+17435+870a78db.x86_64
systemd-239-68.el8_7.2.x86_64
kernel-4.18.0-425.8.1.el8_7.x86_64

[root@ibm-x3650m4-01-vm-05 podman]# bats test/system/220-healthcheck.bats
220-healthcheck.bats
 ✓ podman healthcheck
   setup(): removing stray image localhost/healthcheck_i:latest
   setup(): removing stray image a1d497ff18da
   setup(): removing stray image <none>:<none>
   setup(): removing stray image 6a5843e0c493
   setup(): removing stray image <none>:<none>
   setup(): removing stray image 8d7b733a24c1
   setup(): removing stray image <none>:<none>
   setup(): removing stray image c118544c30dd
 ✓ podman healthcheck - restart cleans up old state
 ✓ podman healthcheck --health-on-failure
   setup(): removing stray image localhost/healthcheck_i:latest
   setup(): removing stray image 0c084f5ee49a
   setup(): removing stray image <none>:<none>
   setup(): removing stray image 7b88a1fdce42
   setup(): removing stray image <none>:<none>
   setup(): removing stray image d3f27e14176f
   setup(): removing stray image <none>:<none>
   setup(): removing stray image 3b1392f357d3

3 tests, 0 failures
Comment 10 errata-xmlrpc 2023-01-12 09:24:07 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-2023:0115