Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1200147

Summary:	the 'test' database is no longer provided by default
Product:	Red Hat Software Collections	Reporter:	Honza Horak <hhorak>
Component:	mariadb	Assignee:	Honza Horak <hhorak>
Status:	CLOSED ERRATA	QA Contact:	Branislav Blaškovič <bblaskov>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rh-mariadb100	CC:	bblaskov, databases-maint, hhorak, kvolny, qe-baseos-apps
Target Milestone:	beta
Target Release:	2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rh-mariadb100-mariadb-10.0.17-3.el6, rh-mariadb100-mariadb-10.0.17-3.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1194611	Environment:
Last Closed:	2015-06-04 08:39:51 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:
Bug Depends On:	1194611
Bug Blocks:

Description Honza Horak 2015-03-09 20:34:25 UTC

This change seems to be reasonable, so cloning for mariadb as well.

+++ This bug was initially created as a clone of Bug #1194611 +++

Description of problem:
mysql-server used to provide a database named 'test' by default, which could have been used for mysql client that required a database name to be specified but didn't manipulate any data
in rh-mysql56, the 'test' database is no longer created by default, breaking everything that relied on its existence

<snip>

--- Additional comment from Honza Horak on 2015-03-09 16:30:51 EDT ---

So, I've checked this change with upstream and the `test` db is removed in upstream (since 5.7) from default installation, being it considered a security issue. Thus, the tests should create the `test` database if they use it.

Comment 5 errata-xmlrpc 2015-06-04 08:39:51 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://rhn.redhat.com/errata/RHEA-2015-1062.html