Bug 1510599

Summary: MariaDB/MySQL APB should use service name for binding
Product: OpenShift Container Platform Reporter: cchase
Component: Service BrokerAssignee: cchase
Status: CLOSED ERRATA QA Contact: Weihua Meng <wmeng>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.7.0CC: aos-bugs, chezhang, wmeng, xtian
Target Milestone: ---   
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:

Description cchase 2017-11-07 19:03:19 UTC 
Description of problem:
The binding for the MariaDB APB and MySql APB list the cluster_ip as the DB_HOST.  We should be using the service_name instead.


How reproducible:
100%


Steps to Reproduce:
1. Provision MariaDB/MySQL using APB
2. Create Binding for provisioned service
3. View secret
4. Reveal secret

Actual results:
DB_HOST: 123.123.123.123 
# Cluster IP address is shown instead of the service name.

Expected results:
DB_HOST: rhscl-mariadb (or mysql)
# service name is shown as DB_HOST


Additional info:
Binding to an application must still work with no regressions.
Comment 1 cchase 2017-11-07 19:06:40 UTC 
https://github.com/ansibleplaybookbundle/rhscl-mariadb-apb/pull/11
https://github.com/ansibleplaybookbundle/rhscl-mysql-apb/pull/12
Comment 3 Weihua Meng 2017-11-08 08:41:45 UTC 
Waiting for new image in stage to test.
Comment 4 Weihua Meng 2017-11-09 06:21:50 UTC 
Fixed in 
openshift3/mysql-apb:v3.7.0-0.198.0.3
DB_HOST mysql

openshift3/mariadb-apb:v3.7.0-0.198.0.3
DB_HOST rhscl-mariadb

openshift3/postgresql-apb:v3.7.0-0.198.0.3
DB_HOST postgresql
Comment 7 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