Bug 1534883

Summary:	[ASB] Provision APBs failed by docker run
Product:	OpenShift Container Platform	Reporter:	Jian Zhang <jiazha>
Component:	Service Broker	Assignee:	Derek Whatley <dwhatley>
Status:	CLOSED ERRATA	QA Contact:	Jian Zhang <jiazha>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.9.0	CC:	aos-bugs, chezhang, dwhatley, dzager, jiazha, jmatthew
Target Milestone:	---
Target Release:	3.9.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-03-28 14:19:53 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:
Bug Depends On:
Bug Blocks:	1523168

Comment 12 David Zager 2018-01-26 08:00:20 UTC

@JianZhang, the failure that you are seeing is because the container being run does not have the POD_NAME & POD_NAMESPACE environment variables set. You could, potentially set them, but I would have no expectation for that to work since you are not a pod running in the cluster.

As an aside, I see in your comment, "I also test it with specifying the `--extra-vars 'runtime=2'` and --extra-vars 'runtime=1', still got the same errors." The runtime versions do not work this way and are inherited in the image you are using, you can't manipulate the runtime version.

The fact that our APBs are container images that can be run with `docker run ...` is great. However, there should be no expectation for the https://github.com/ansibleplaybookbundle/ansible-asb-modules to work in an APB run outside the context of the Ansible Service Broker. At best, this is an issue against the postgresql-apb to handle execution outside of the broker context.

Comment 18 errata-xmlrpc 2018-03-28 14:19:53 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:0489