Bug 1741157

Summary:	exit status from command run in container not forwarded to outside
Product:	Red Hat Enterprise Linux 8	Reporter:	Jan Blazek <jblazek>
Component:	podman	Assignee:	Brent Baude <bbaude>
Status:	CLOSED ERRATA	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	ajia, dornelas, dwalsh, hhorak, jligon, jnovy, lsm5, mdomonko, mheon, miabbott, santiago, vavuthu, wchadwic, wjiang
Target Milestone:	rc	Keywords:	Regression, TestBlocker
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 21:02:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan Blazek 2019-08-14 11:38:11 UTC

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.

Comment 2 Michal Domonkos 2019-08-14 11:56:45 UTC

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

Comment 13 Abhinav Dahiya 2019-09-09 16:30:21 UTC

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

Comment 15 Abhinav Dahiya 2019-09-11 17:56:15 UTC

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

Comment 17 Alex Jia 2019-09-27 07:45:30 UTC

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

Comment 19 errata-xmlrpc 2019-11-05 21:02:57 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, 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