Bug 1380847
| Summary: | atomic containers delete --all useless error message | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Chris Evich <cevich> |
| Component: | atomic | Assignee: | Lokesh Mandvekar <lsm5> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | ajia, dwalsh |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-06 17:42:03 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: | |||
Note: Same behavior with or without the --force option. It seems I can get an expected error like this "Conflict, You cannot remove a running container. Stop the container before attempting removal or use -f". [root@atomic-host-001 cloud-user]# cat /etc/redhat-release Red Hat Enterprise Linux Atomic Host release 7.3 [root@atomic-host-001 cloud-user]# rpm -q atomic docker atomic-1.12.5-2.el7.x86_64 docker-1.10.3-55.el7.x86_64 This bug has been fixed in Atomic Host 7.3.
[root@atomic-host-001 cloud-user]# cat /etc/redhat-release
Red Hat Enterprise Linux Atomic Host release 7.3
[root@atomic-host-001 cloud-user]# rpm -q atomic docker
atomic-1.12.5-2.el7.x86_64
docker-1.10.3-55.el7.x86_64
[root@atomic-host-001 cloud-user]# for i in {1..6};do docker run -itd --name busybox_$i busybox /bin/sh;done
48e7f3df0e2ad045c5c0191d60a0f6339350a498ec52ad2200b284ef2b373246
532cd20166f4c3362e4722511858e80fa550361a33c8e1745219ecb2417e5168
42df365b2ba9910df1a9b865ef386b2fbd3d2d85e8094e69f15cdf7933c68b15
0eeff89145b79d0f72b77f464f71223e2ef41643749d4818703318aa33351d66
8992c6b7934c0c65273956a245b946016a71ee93639cbc4bb94d8635b25c1466
5f85260bc00509597c95cea6cd41af1768cbf3c3fd4e061adcee6011a34c3e2b
[root@atomic-host-001 cloud-user]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5f85260bc005 busybox "/bin/sh" 5 seconds ago Up 3 seconds busybox_6
8992c6b7934c busybox "/bin/sh" 7 seconds ago Up 5 seconds busybox_5
0eeff89145b7 busybox "/bin/sh" 9 seconds ago Up 7 seconds busybox_4
42df365b2ba9 busybox "/bin/sh" 10 seconds ago Up 9 seconds busybox_3
532cd20166f4 busybox "/bin/sh" 12 seconds ago Up 10 seconds busybox_2
48e7f3df0e2a busybox "/bin/sh" 13 seconds ago Up 12 seconds busybox_1
[root@atomic-host-001 cloud-user]# atomic containers delete -f --all
[root@atomic-host-001 cloud-user]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
Fixed in atomic -1.13 It also works in atomic-1.13.3-1.el7.x86_64. 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://rhn.redhat.com/errata/RHBA-2016-2857.html |
Description of problem: Version-Release number of selected component (if applicable): atomic-1.12.3-2.el7.x86_64 docker-1.10.3-55.el7.x86_64 How reproducible: highly Steps to Reproduce: 1. # for n in $(seq 1 6); do docker run -d --name rhel${n} rhel sleep ${n}h; done 2. atomic containers delete --all Actual results: 'Type' (exit code 1) Expected results: A useful error message that some or all containers could not be deleted because they are still running. Additional info: