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 1313555 - atomic uninstall gives non-zero exit
Summary: atomic uninstall gives non-zero exit
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sadc-container
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jeremy Eder
QA Contact: atomic-bugs@redhat.com
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-01 21:53 UTC by Chris Evich
Modified: 2016-05-12 16:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-12 16:56:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1067 0 normal SHIPPED_LIVE Red Hat Enterprise Linux Atomic sadc Container Image Update 2016-05-12 20:55:34 UTC

Description Chris Evich 2016-03-01 21:53:12 UTC
Description of problem:
When uninstalling, the script tries to remove an existing sadc container.  That works fine, unless no container was started, or it was already removed (manually).  In that case, the script returns non-zero exit status when it shouldn't (since removing the container was the goal).

Version-Release number of selected component (if applicable):

registry.access.redhat.com/rhel7/sadc         latest              96ca6a153fd6        16 hours ago        215 MB

How reproducible:
Trivial

Steps to Reproduce:
1. atomic install registry.access.redhat.com/rhel7/sadc:latest
2. atomic uninstall registry.access.stage.redhat.com/rhel7/sadc:latest

Actual results:
-bash-4.2# atomic uninstall registry.access.stage.redhat.com/rhel7/sadc:latest
docker run --rm --privileged -v /:/host -e HOST=/host -v /var/log:/var/log -e IMAGE=registry.access.stage.redhat.com/rhel7/sadc:latest -e NAME=sadc registry.access.stage.redhat.com/rhel7/sadc:latest /usr/local/bin/sysstat-uninstall.sh ; docker rm -f sadc
Error response from daemon: no such id: sadc
Error: failed to remove containers: [sadc]
-bash-4.2# echo $?
1

Expected results:
-bash-4.2# atomic uninstall registry.access.stage.redhat.com/rhel7/sadc:latest
docker run --rm --privileged -v /:/host -e HOST=/host -v /var/log:/var/log -e ...whatever...
-bash-4.2# echo $?
0


Additional info:
The rsyslog image uninstall does not have this problem

Comment 5 errata-xmlrpc 2016-05-12 16:56:41 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-1067.html


Note You need to log in before you can comment on or make changes to this bug.