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.

Created attachment 1606077 [details]
podman --log-level=debug run --rm alpine true

Command hangs for as long as I'm willing to wait (many minutes). ^C results in:

   $ podman run --rm alpine true
   ^C
   ERRO[0041] Error forwarding signal 2 to container d8223a16ec0a64015d1ebaae0a624cbe833d3b4f3c90d253e22d4dbfed2e62ed: container has already been removed

   ERRO[0041] Error forwarding signal 15 to container d8223a16ec0a64015d1ebaae0a624cbe833d3b4f3c90d253e22d4dbfed2e62ed: container has already been removed

This is only with --rm. Plain 'podman run alpine true' exits 0 as expected.

podman-1.4.2-2.module+el8.1.0+3888+8b36fd52.x86_64

it seems to be caused by an old conmon.  We'll need to upgrade the conmon package.

Is this a change to the spec file or are we now using the separately packaged conmon?

Jindrich, could you make sure we have the latest conmon shipping with Podman in RHEL8.

Test with podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64 given steps with and the command can finished as expect, so set this to verified.
Details:
$ time podman run --rm alpine true

real	0m0.655s
user	0m0.130s
sys	0m0.131s

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