Bug 1507321 - Cannot access Mediawiki123 route after binding to MySQL
Summary: Cannot access Mediawiki123 route after binding to MySQL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 3.7.0
Assignee: cchase
QA Contact: Zhang Cheng
URL: devel
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-29 16:53 UTC by Zhang Cheng
Modified: 2017-11-28 22:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-11-28 22:20:01 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

Comment 1 cchase 2017-10-30 19:46:15 UTC 
https://github.com/ansibleplaybookbundle/rhscl-mysql-apb/pull/7

The binding parameters on mysql were not set to the env vars needed by mediawiki.  I've changed them to match.  If you look at the created secret when binding you'll notice the vars:

Old:
  MYSQL_DATABASE: 
  MYSQL_HOST:
  MYSQL_PASSWORD: 
  MYSQL_PORT: 
  MYSQL_USER: 

New:
  DB_HOST: 
  DB_NAME: 
  DB_PASSWORD: 
  DB_PORT: 
  DB_TYPE: 
  DB_USER: 

The new vars should allow the mysql binding to work properly with mediawiki and be more generic should other applications want to be able to switch between databases.
Comment 2 Zhang Cheng 2017-11-03 06:36:06 UTC 
Verified with Latest APB images, can access Mediawiki123 route after binding to MySQL. Thanks.
Comment 5 errata-xmlrpc 2017-11-28 22:20:01 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.