Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1761608

Summary:	After killing the ansible-runner-service container the old container remains
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Paul Cuzner <pcuzner>
Component:	Ceph-Installer	Assignee:	Paul Cuzner <pcuzner>
Status:	CLOSED ERRATA	QA Contact:	Tejas <tchandra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	aschoen, ceph-eng-bugs, ceph-qe-bugs, nthomas, tserlin, ykaul
Target Milestone:	rc
Target Release:	4.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	cockpit-ceph-installer-0.9-2.el8cp	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-31 12:47:33 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:

Description Paul Cuzner 2019-10-14 21:13:12 UTC

Description of problem:
The cockpit-ceph-installer package provides a command to start and stop the ansible runner API. However, when using the -k option to stop the container the image is not removed, which prevents the container from being restarted.

Version-Release number of selected component (if applicable):
cockpit-ceph-installer 0.9-1

How reproducible:
every time


Steps to Reproduce:
1. run ansible-runner-service.sh -s to start the container
2. ansible-runner-service.sh -k to stop the container
3. use podman/docker to see the container image is still present

Actual results:
container is not removed

Expected results:
container should be removed by a -k operation


Additional info:

Comment 1 Paul Cuzner 2019-10-15 22:53:28 UTC

two commits address this issue d2eb86540314acecd232dd32ec78cc231f17d2cf and 292d0bf9c5a191780b60337dc6f6395faac7ce6a

Comment 5 errata-xmlrpc 2020-01-31 12:47:33 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-2020:0312