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:

Podman is extremely slow on systems under heavy I/O load. 

Version-Release number of selected component (if applicable):

Podman 1.4.2 (as build for RHEL 8.1 and Fedora - reproduces on both)

How reproducible:

100%, though severity varies based on the system it is run on

Steps to Reproduce:
1. In terminal 1, run a few containers (`podman run -t -i -d alpine top` works, but the exact contents don't matter)
2. In terminal 2: `dd if=/dev/zero of=<file on same FS as /var/lib/containers> bs=1M`
3. Back in terminal 1: `time podman info` (All other Podman commands except version also affected)
4. Stop the `dd` in terminal 2 and delete the file

Actual results:

The `podman info` in command 3 takes approximately 90 seconds to complete

Expected results:

A more reasonable execution time - a few seconds at most

Additional info:

Problem is caused by several disk writes that are holding execution waiting for the disk. While some writes are unavoidable, we can make Podman's fastpast avoid them in almost all cases.

We have patches upstream that reduce execution time from 90 seconds down to around 4 on our test system.

*** Bug 1718230 has been marked as a duplicate of this bug. ***

Test with podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64, and time the podman info for several times, normally it will take less than 1 second to get the output. But sometimes it takes 6 or 7 seconds. All of these are fit a few seconds. So set this to verified.

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, 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/RHSA-2019:3403