Bug 1565790

Summary:	[apb-base] Ansible in apb-base image should not create retry files
Product:	OpenShift Container Platform	Reporter:	David Zager <dzager>
Component:	Service Broker	Assignee:	Michael Hrivnak <mhrivnak>
Status:	CLOSED ERRATA	QA Contact:	Jian Zhang <jiazha>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.10.0	CC:	aos-bugs, chezhang, jiazha, zhsun, zitang
Target Milestone:	---
Target Release:	3.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-30 19:12:35 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 David Zager 2018-04-10 19:31:51 UTC

Description of problem:

Typically, when using ansible, retry files are very helpful for...retrying. However, in the containerized Ansible case there is no need to create these.

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


How reproducible: Always


Steps to Reproduce:
1. docker run --entrypoint /bin/bash docker.io/ansibleplaybookbundle/apb-base:latest
2. cat /etc/ansible/ansible.cfg

Expected results:

The file should include "retry_files_enabled = False"

Comment 1 David Zager 2018-04-10 19:33:14 UTC

https://github.com/ansibleplaybookbundle/apb-base/pull/15

Comment 2 Jian Zhang 2018-04-26 07:04:14 UTC

Verify succeed. Details as below:

[root@host-172-16-120-36 ~]# docker inspect docker.io/ansibleplaybookbundle/apb-base --format "{{ index .Created}}"
2018-04-25T16:19:52.420021535Z

[root@host-172-16-120-36 ~]# docker run -ti --entrypoint /bin/bash docker.io/ansibleplaybookbundle/apb-base:latest
bash-4.2# ls
ansible.cfg  etc  hosts
bash-4.2# cat ansible.cfg 
[defaults]
retry_files_enabled = False
inventory = /opt/apb/hosts
roles_path = /etc/ansible/roles:/opt/ansible/roles

Comment 4 errata-xmlrpc 2018-07-30 19:12:35 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-2018:1816