Bug 1614173 – Mysql APB provision failed while using galaxy registry

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1614173 - Mysql APB provision failed while using galaxy registry

Summary:	Mysql APB provision failed while using galaxy registry

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Service Broker (Show other bugs)
Sub Component:
Version:	3.11.0
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	3.11.0
Assigned To:	David Zager
QA Contact:	Zhang Cheng
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-08-09 02:48 EDT by Zhang Cheng
Modified:	2018-10-11 03:24 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-10-11 03:24:08 EDT
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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:2652	None	None	None	2018-10-11 03:24 EDT

Groups: None (edit)

Comment 1 David Zager 2018-08-09 10:59:08 EDT

Had an issue with the versions that were being saved on the Galaxy server. Should be addressed now.

Comment 2 Zhang Cheng 2018-08-09 23:34:42 EDT

mysql in Galaxy Server have been updated. Provision succeed. Verified and Passed.

Comment 4 errata-xmlrpc 2018-10-11 03:24:08 EDT

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/RHBA-2018:2652

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