Bug 1380848
| Summary: | atomic containers delete is parameter order dependent | ||
|---|---|---|---|
| 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, cnegus, 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:08 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: | 1389707 | ||
| Bug Blocks: | |||
(In reply to Chris Evich from comment #0) > Additional info: > An easy fix could be to update the --help (usage) information to reflect > that parameter order is important. The more "friendly" fix is to assume all > parameters beginning with '--' are options, unless they're preceded by a > (throw away) '--' parameter. Yes, it should be enough to update document I think, because docker has the same issue if we don't consider parameter order. [root@atomic-host-001 cloud-user]# docker rm e5881ac96cc6 --force Failed to remove container (e5881ac96cc6): Error response from daemon: Conflict, You cannot remove a running container. Stop the container before attempting removal or use -f Failed to remove container (--force): Error response from daemon: No such container: --force https://github.com/projectatomic/atomic/pull/690 Should clean this up Fixed in atomic-1.13 > Yes, it should be enough to update document I think,
I agree, documentation/--help fix is totally cool
[root@atomic-00 cloud-user]# cat /etc/redhat-release Red Hat Enterprise Linux Atomic Host release 7.3 [root@atomic-00 cloud-user]# rpm -q atomic atomic-1.13.5-1.el7.x86_64 [root@atomic-00 cloud-user]# atomic containers delete -h usage: atomic containers delete [-h] [-f] [-a | container] positional arguments: container Specify one or more containers. Must be final arguments. optional arguments: -h, --help show this help message and exit -f, --force Force removal of specified running containers -a, --all Delete all containers 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: atomic containers delete is parameter order dependent Version-Release number of selected component (if applicable): docker-1.10.3-55.el7.x86_64 atomic-1.12.3-2.el7.x86_64 How reproducible: trivial Steps to Reproduce: 1. docker run -d --name rhel rhel sleep 1h 2. atomic containers delete 1288ad0e7049 --force Actual results: Failed operation for delete container 1288ad0e7049: 409 Client Error: Conflict ("Conflict, You cannot remove a running container. Stop the container before attempting removal or use -f") Failed to delete container --force: 404 Client Error: Not Found ("No such container: --force") (exit code 2) Expected results: Container 1288ad0e7049 is forcibly deleted Additional info: An easy fix could be to update the --help (usage) information to reflect that parameter order is important. The more "friendly" fix is to assume all parameters beginning with '--' are options, unless they're preceded by a (throw away) '--' parameter.