Bug 1510599 - MariaDB/MySQL APB should use service name for binding
Summary: MariaDB/MySQL APB should use service name for binding
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.7.0
Assignee: cchase
QA Contact: Weihua Meng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-07 19:03 UTC by cchase
Modified: 2017-11-28 22:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-11-28 22:21:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 0 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-29 02:34:54 UTC

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 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


Note You need to log in before you can comment on or make changes to this bug.