Bug 1511077
Summary: | Mediawiki cannot bind to MySql/MariaDB | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | cchase |
Component: | Service Broker | Assignee: | Jason Montleon <jmontleo> |
Status: | CLOSED ERRATA | QA Contact: | Zhang Cheng <chezhang> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.7.0 | CC: | aos-bugs, jmatthew, 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-08 15:53:47 UTC
We appear to be missing several optional php packages, including php-mysql, downstream. Working on updating the image. To clarify upstream canary versions of Mediawiki are not affected by this bug. mediawiki-123:v3.7.0-0.198.1.1 will work with the mysql apb now. We found a separate issue in mariadb when a random password is generated that will necessitate rebuilding the mariadb APB role and container. the latest mariadb-apb container will fix the second issue. In fact, I'm not sure my problem have same root cause with this bug. That because only said while binding to MySql/MariaDB in original description, but all three DB failed in my testing. Please help to confirm and review if it is a block issue for ocp3.7 GA. The only images that are likely to fully work right now are 3.7.4-2 and 3.7.5-2 when I get them built shortly. Since the puddles started incrementing versions from 3.7.0 we've been getting containers with very old images. We're trying to find out from someone what's going on. Jason, That is OKay for me. Thanks your explanation. 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 |