Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Descriptionsthirugn@redhat.com
2016-04-05 20:23:07 UTC
Description of problem:
deleting a container in hammer is successful but the container is not actually removed from external docker compute resource
Version-Release number of selected component (if applicable):
Satellite-6.2-beta-snap6.1
How reproducible:
Always
Steps to Reproduce:
1. Create an external docker compute resource
2. Create a docker container using the external docker computer resource
3. delete the docker container using hammer
# hammer -u admin -p changeme docker container list
---|--------------|----------------------------------------------------------------|--------|---------|-----------------
ID | NAME | IMAGE REPOSITORY | TAG | COMMAND | COMPUTE RESOURCE
---|--------------|----------------------------------------------------------------|--------|---------|-----------------
5 | container_02 | default_organization-dev1-docker_cv-dockerproduct1-dockerrepo1 | latest | top | docker_cr
---|--------------|----------------------------------------------------------------|--------|---------|-----------------
# hammer -u admin -p changeme docker container delete --name container_02
Docker container deleted
# hammer -u admin -p changeme docker container list
---|------|------------------|-----|---------|-----------------
ID | NAME | IMAGE REPOSITORY | TAG | COMMAND | COMPUTE RESOURCE
---|------|------------------|-----|---------|-----------------
Actual results:
Hammer delete was successful as shown above. But
* Container is still shown as running in Satellite UI
* Container is still running in the external docker compute resource
Expected results:
Container should be removed from Satellite UI too.
Container should be removed in external docker compute resource too.
Additional info:
Comment 2Daniel Lobato Garcia
2016-04-07 08:15:14 UTC
Comment 3Daniel Lobato Garcia
2016-04-07 08:40:03 UTC
Containers deletion does work on the UI but the API is using a different method. I'll create a service so both use the same method for deleting containers - the API was just removing the Foreman object instead of making a delete call to the Docker API
Comment 4Daniel Lobato Garcia
2016-04-07 14:37:08 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://access.redhat.com/errata/RHBA-2016:1501