Incomplete fix for bug #710799

Bug #1169522 reported by Alexey Kopytov on 2013-04-16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona Server moved to
Fix Released
Ignacio Nin
Fix Released
Ignacio Nin
Fix Released
Ignacio Nin
Fix Released
Ignacio Nin

Bug Description

As reported in the fix for bug #710799 was incomplete. When an upgrade is performed between major versions (e.g. by uninstalling a 5.1 RPM and then installing a 5.5 one), mysql_install_db is still called on the existing data directory which leads to re-creation of the test database.

Tags: pkg Edit Tag help

Related branches

tags: added: pkg
Alexey Bychko (abychko) wrote :

performing clean installation of 5.5 with databases from erased 5.1
+ '[' 1 -eq 1 ']'
+ '[' '!' -d /var/lib/mysql ']'
+ '[' -f /var/lib/mysql/RPM_UPGRADE_MARKER ']'
++ grep '^SERVER_TO_START=' /var/lib/mysql/RPM_UPGRADE_MARKER
++ cut -c17-
+ '[' '!' -d /var/lib/mysql/mysql ']'
+ echo 'MySQL RPM upgrade to version 5.5.30-rel30.2.502.rhel6'
+ '[' '!' -d /var/lib/mysql/test ']'
+ /usr/bin/mysql_install_db --rpm --user=mysql
ERROR: 1136 Column count doesn't match value count at row 1
130416 12:04:47 [ERROR] Aborting
130416 12:04:47 [Note] /usr/sbin/mysqld: Shutdown complete

Alexey Bychko (abychko) wrote :

i think "Incomplete fix for bug #710799" is wrong title for this bug.
from technical point of view it's just clean installation of 5.5 after manual 5.1 uninstalling (it doesn't matter, see below).

database files in defailt location may be left by:
* mysql from linux distribution
* Oracle MySQL - any version
* MariaDB - any version
* PS - any version
* or, be just a garbage

so, IMHO proper title for this bug should be like "PS should try to handle/repair databases in %post if any found in default location"

Percona now uses JIRA for bug reports so this bug report is migrated to:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers