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's exit status is 0 despite the exit status of the command run in container is not 0.

DNF upstream test suite (https://github.com/rpm-software-management/ci-dnf-stack) relies on this behaviour and it's a test blocker for us.
I think it is a significant API breakage and many other workflows could rely on this.


Version-Release number of selected component (if applicable):
podman-1.4.2-2.module+el8.1.0+3888+8b36fd52.x86_64

How reproducible:
always

Steps to Reproduce:
# podman pull fedora:latest
# podman run --rm fedora false
# echo $?
0

Actual results:
Podman's exit status is 0.

Expected results:
Podman's exit status should be 1.

Additional info:
Previous version podman-1.4.2-1.module+el8.1.0+3423+f0eda5e0.x86_64 used to work OK. This must be a regression of newest version.
This occurs only with --rm parameter passed to run subcommand. Without --rm the exit status is propagated as expected.

FYI, the Fedora version of podman (1.4.4-4.fc30) works fine.

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

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

I can reproduce this issue in podman-1.4.2-2.module+el8.1.0+3888+8b36fd52.x86_64,
and verified in podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64.

[root@kvm-06-guest17 ~]# rpm -q podman
podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64

[root@kvm-06-guest17 ~]# podman run --rm fedora false
[root@kvm-06-guest17 ~]# echo $?
1

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