Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1507321 - Cannot access Mediawiki123 route after binding to MySQL
Cannot access Mediawiki123 route after binding to MySQL
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
3.7.0
Unspecified Unspecified
high Severity medium
: ---
: 3.7.0
Assigned To: cchase
Zhang Cheng
devel
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-10-29 12:53 EDT by Zhang Cheng
Modified: 2017-11-28 17:20 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-28 17:20:01 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-28 21:34:54 EST

  None (edit)
Comment 1 cchase 2017-10-30 15:46:15 EDT
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 02:36:06 EDT
Verified with Latest APB images, can access Mediawiki123 route after binding to MySQL. Thanks.
Comment 5 errata-xmlrpc 2017-11-28 17:20:01 EST
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.