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 1380850 - atomic containers delete <NULL> silently succeeds
Summary: atomic containers delete <NULL> silently succeeds
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
medium
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 19:02 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:12 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 19:02:09 UTC
Description of problem:


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. # atomic containers delete $(echo -e "\000")

Actual results:
(no output)
(exit code 0)

Expected results:
Some kind of 'invalid', 'missing', or 'unknown' argument message and a non-zero exit.

Additional info:

Comment 2 Alex Jia 2016-10-10 08:49:22 UTC
The same issue in atomic-1.12.5-2.el7.x86_64.

Comment 3 Daniel Walsh 2016-10-10 15:01:25 UTC
https://github.com/projectatomic/atomic/pull/689 should fix this.

Comment 4 Daniel Walsh 2016-10-12 19:04:45 UTC
Fixed in atomic-1.13

Comment 6 Alex Jia 2016-10-28 09:29:51 UTC
I can get an expected result like the following error now.

[root@atomic-host-001 cloud-user]# atomic containers delete $(echo -e "\000")
Expected a string but found [None] (<type 'list'>) instead

[root@atomic-host-001 cloud-user]# atomic host status
State: idle
Deployments:
● rhel-atomic-host:rhel-atomic-host/7/x86_64/standard
       Version: 7.3 (2016-10-26 14:24:09)
        Commit: 90c9735becfff1c55c8586ae0f2c904bc0928f042cd4d016e9e0e2edd16e5e97
        OSName: rhel-atomic-host
  GPGSignature: (unsigned)
      Unlocked: development

[root@atomic-host-001 cloud-user]# rpm -q atomic
atomic-1.13.3-1.el7.x86_64

Comment 8 errata-xmlrpc 2016-12-06 17:42:12 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.