main.mysql_upgrade fails on 11.0

Bug #588182 reported by Aleksandr Kuzminsky
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Invalid
Undecided
Aleksandr Kuzminsky

Bug Description

main.mysql_upgrade [ fail ]
        Test ended at 2010-06-01 02:33:25

CURRENT_TEST: main.mysql_upgrade
--- /home/buildbot/slaves/percona-server-51-11/CentOS-5-x86-64/build/Percona-Server/mysql-test/r/mysql_upgrade.result 2010-05-06 18:58:53.000000000 +0300
+++ /home/buildbot/slaves/percona-server-51-11/CentOS-5-x86-64/build/Percona-Server/mysql-test/r/mysql_upgrade.reject 2010-06-01 09:34:25.000000000 +0300
@@ -94,7 +94,7 @@
 mysql.user OK
 DROP USER mysqltest1@'%';
 Run mysql_upgrade with a non existing server socket
-mysqlcheck: Got error: 2005: Unknown MySQL server host 'not_existing_host' (errno) when trying to connect
+mysqlcheck: Got error: 2003: Can't connect to MySQL server on 'not_existing_host' (errno) when trying to connect
 FATAL ERROR: Upgrade failed
 set GLOBAL sql_mode='STRICT_ALL_TABLES,ANSI_QUOTES,NO_ZERO_DATE';
 mtr.global_suppressions OK

mysqltest: Result content mismatch

Related branches

Changed in percona-server:
milestone: none → 5.1-11.0
assignee: nobody → Aleksandr Kuzminsky (akuzminsky)
Changed in percona-server:
status: New → In Progress
Revision history for this message
Aleksandr Kuzminsky (akuzminsky) wrote :

The problem goes down to wrong DNS configuration.

MySQL client tries to connect to non-existing hostname 'invalid_hostname'. It expects to
get error 2005, which means 'invalid_hostname' can't get resolved. But if it is resolved
MySQL gets error 2003 (Can't connect to MySQL server).

Check
$ host invalid_hostname

If the request is resolved - it is bad.

Changed in percona-server:
status: In Progress → Invalid
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2525

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.