Bug 1510299

Summary:	mariadb and mysql provision failed at cannot access /etc/apb-secrets while using rhcc registry
Product:	OpenShift Container Platform	Reporter:	Zhang Cheng <chezhang>
Component:	Service Broker	Assignee:	Jason Montleon <jmontleo>
Status:	CLOSED ERRATA	QA Contact:	Zhang Cheng <chezhang>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.7.0	CC:	aos-bugs, jmatthew, jmontleo, wmeng
Target Milestone:	---	Keywords:	TestBlocker
Target Release:	3.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-28 22:21:49 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:

Comment 1 Jason Montleon 2017-11-07 14:33:25 UTC

The ls /etc/apb-secrets error isn't causing the APB to fail, though this should fix it, https://github.com/ansibleplaybookbundle/apb-base/pull/5

The failure is due to include_tasks being used with ansible 2.3.

We have updated the packages again (to use include_tasks) and we're getting ansible 2.4.0 on our downstream apb-base image now so all the deprecations and errors should hopefully sort out in the next puddle or so.

Comment 2 Jason Montleon 2017-11-07 14:52:43 UTC

apb-base-scripts-1.0.5-1.el7 should fix the ls /etc/apb-secrets error.

A separate BZ exists for the include_tasks and ansible 2.4.0 work (though not for the errors your seeing specifically) and these should hopefully clear up as I believe that work is done as well.

Comment 5 Jason Montleon 2017-11-08 13:32:33 UTC

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

Comment 6 Zhang Cheng 2017-11-09 09:17:59 UTC

Verified with latest images in rhcc reigstry:
apb-base:v3.7.4-2
mysql-apb:v3.7.4-2
mariadb-apb:v3.7.4-2

Comment 9 errata-xmlrpc 2017-11-28 22:21:49 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/RHSA-2017:3188