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.
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