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.
Bug 1380847 - atomic containers delete --all useless error message
Summary: atomic containers delete --all useless error message
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: atomic
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-30 18:42 UTC by Chris Evich
Modified: 2016-12-06 17:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-06 17:42:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2857 0 normal SHIPPED_LIVE atomic bug fix and enhancement update 2016-12-06 22:40:27 UTC

Description Chris Evich 2016-09-30 18:42:32 UTC 
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:
Comment 1 Chris Evich 2016-09-30 18:44:08 UTC 
Note: Same behavior with or without the --force option.
Comment 3 Alex Jia 2016-10-08 09:43:12 UTC 
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
Comment 4 Alex Jia 2016-10-10 08:47:41 UTC 
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
Comment 5 Daniel Walsh 2016-10-10 14:47:29 UTC 
Fixed in  atomic -1.13
Comment 7 Alex Jia 2016-10-28 09:32:59 UTC 
It also works in atomic-1.13.3-1.el7.x86_64.
Comment 9 errata-xmlrpc 2016-12-06 17:42:03 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://rhn.redhat.com/errata/RHBA-2016-2857.html
Note You need to log in before you can comment on or make changes to this bug.