Bug 1723470
Summary: | podman exec rc-code needs to distinguish between stopped containers and non existing ones [rhel-8.0.0.z] | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Oneata Mircea Teodor <toneata> |
Component: | podman | Assignee: | Brent Baude <bbaude> |
Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
Severity: | high | Docs Contact: | |
Priority: | urgent | ||
Version: | 8.0 | CC: | atomic-bugs, ddarrah, dornelas, dwalsh, jligon, jnovy, lmiccini, lsm5, mheon, michele, pthomas, wchadwic, ypu |
Target Milestone: | rc | Keywords: | ZStream |
Target Release: | 8.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | podman-1.0.2-1.git4426985.module+el8.0.0.z+3525+56c076c3 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1719626 | Environment: | |
Last Closed: | 2019-07-30 19:50:31 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: | |||
Bug Depends On: | 1719626 | ||
Bug Blocks: | 1727325 |
Comment 2
Daniel Walsh
2019-06-24 16:42:59 UTC
Test with podman-1.0.3-1.git9d78c0c.module+el8.0.0.z+3717+fdd07b7c.x86_64. And seems the exit code already updated. So set this to verified, Details: # podman exec memcached /bin/true; echo $? unable to exec into memcached: no container with name or ID memcached found: no such container 125 # podman ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES eb4605318818 docker.io/library/busybox:latest sh 8 seconds ago Exited (0) 8 seconds ago unruffled_mirzakhani # podman exec eb4605318818 /bin/true ; echo $? cannot exec into container that is not running: container state improper 126 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/RHBA-2019:1956 |