percona server outputs wrong version_comment in ubuntu/debian

[Muhammad Irfan]

I've begun testing upgrades from Percona Server 5.6.15 to 5.6.17 and noticed the banner message when I request the version does not include Percona. This looks similar to it https://bugs.launchpad.net/percona-server/+bug/1319670
Also, i found the same issue with latest PS 5.5

mysql> show global variables like '%version%';
+-------------------------+-------------------------+
| Variable_name | Value |
+-------------------------+-------------------------+
| innodb_version | 5.5.37-35.0-35.0 |
| protocol_version | 10 |
| slave_type_conversions | |
| version | 5.5.37-35.0-657.precise |
| version_comment | (Ubuntu) |
| version_compile_machine | x86_64 |
| version_compile_os | debian-linux-gnu |
+-------------------------+-------------------------+

Ubuntu
======
root@ubuntu12:~# mysqld --version
mysqld Ver 5.6.17-65.0-587.precise for debian-linux-gnu on x86_64 ((Ubuntu))

mysql> show global variables like '%version%';
+-------------------------+-------------------------+
| Variable_name | Value |
+-------------------------+-------------------------+
| innodb_version | 5.6.17-65.0 |
| protocol_version | 10 |
| slave_type_conversions | |
| version | 5.6.17-65.0-587.precise |
| version_comment | (Ubuntu) |
| version_compile_machine | x86_64 |
| version_compile_os | debian-linux-gnu |
+-------------------------+-------------------------+

mysql> status
--------------
mysql Ver 14.14 Distrib 5.6.17-65.0, for debian-linux-gnu (x86_64) using EditLine wrapper

Server version: 5.6.17-65.0-587.precise (Ubuntu)

Debian:
======
# mysqld --version
mysqld Ver 5.6.17-65.0-587.wheezy for debian-linux-gnu on x86_64 ((Debian))

mysql> show global variables like '%version%';
+-------------------------+------------------------+
| Variable_name | Value |
+-------------------------+------------------------+
| innodb_version | 5.6.17-65.0 |
| protocol_version | 10 |
| slave_type_conversions | |
| version | 5.6.17-65.0-587.wheezy |
| version_comment | (Debian) |
| version_compile_machine | x86_64 |
| version_compile_os | debian-linux-gnu |
+-------------------------+------------------------+

mysql> status
--------------
mysql Ver 14.14 Distrib 5.6.17-65.0, for debian-linux-gnu (x86_64) using EditLine wrapper

Server version: 5.6.17-65.0-587.wheezy (Debian)

Below is from previous version which worked fine.

root@ubuntu12:/var/lib/mysql# mysqld --version
mysqld Ver 5.6.15-63.0 for Linux on x86_64 (Percona Server (GPL), Release 63.0)

mysql> show global variables like '%version%';
+-------------------------+------------------------------------+
| Variable_name | Value |
+-------------------------+------------------------------------+
| innodb_version | 5.6.15-rel63.0 |
| protocol_version | 10 |
| slave_type_conversions | |
| version | 5.6.15-63.0 |
| version_comment | Percona Server (GPL), Release 63.0 |
| version_compile_machine | x86_64 |
| version_compile_os | Linux |
+-------------------------+------------------------------------+

mysql> status
--------------
mysql Ver 14.14 Distrib 5.6.15, for Linux (x86_64) using EditLine wrapper

Server version: 5.6.15-63.0 Percona Server (GPL), Release 63.0

[Valerii Kravchuk (valerii-kravchuk)]

I've confirmed this on Ubuntu 13.10 also.

[Ramesh Sivaraman (rameshvs02)]

One more version name difference noticed in innodb_version string in PS-5.5 rpm/deb packages. "-35.1" repeated twice in innodb version name

{code}

Ubuntu
----------

show global variables like '%version%';
+-------------------------+--------------------------------------------------+
| Variable_name | Value |
+-------------------------+--------------------------------------------------+
| innodb_version | 5.5.37-35.1-35.1 |
| protocol_version | 10 |
| slave_type_conversions | |
| version | 5.5.37-35.1 |
| version_comment | Percona Server (GPL), Release 35.1, Revision 666 |
| version_compile_machine | x86_64 |
| version_compile_os | debian-linux-gnu |
+-------------------------+--------------------------------------------------+
7 rows in set (0.00 sec)

mysql>

CentOS
----------

mysql> show global variables like '%version%';
+-------------------------+--------------------------------------------------+
| Variable_name | Value |
+-------------------------+--------------------------------------------------+
| innodb_version | 5.5.37-35.1-35.1 |
| protocol_version | 10 |
| slave_type_conversions | |
| version | 5.5.37-35.1 |
| version_comment | Percona Server (GPL), Release 35.1, Revision 666 |
| version_compile_machine | x86_64 |
| version_compile_os | Linux |
+-------------------------+--------------------------------------------------+
7 rows in set (0.00 sec)

mysql>
{code}

[Roel Van de Paar (roel11)]

See PS-155, Bug 1319670

[Roel Van de Paar (roel11)]

<jaime> Roel: ok. bug appeared starting on 5.6.16

[Tomislav Plavcic (tplavcic)]

I think this is duplicate of the bug1319670 so I will mark it as that. For 5.5 the fix was released in 5.5.37-35.1, and for 5.6 it will be in the next release.
Rameshes comment about innodb_version is only applicable for 5.5 (not 5.6) and probably for rpm/binary also so I'll open a new bug .

[Muhammad Irfan (muhammad-irfan)]

root@ubuntu12:~# mysqld --version
mysqld Ver 5.1.73-rel14.11 for debian-linux-gnu on x86_64 ((Percona Server (GPL), 14.11, Revision 603))

mysql> show global variables like '%version%';
+-------------------------+---------------------------------------------+
| Variable_name | Value |
+-------------------------+---------------------------------------------+
| innodb_version | 5.1.73-14.11 |
| protocol_version | 10 |
| version | 5.1.73-rel14.11 |
| version_comment | (Percona Server (GPL), 14.11, Revision 603) |
| version_compile_machine | x86_64 |
| version_compile_os | debian-linux-gnu |
+-------------------------+---------------------------------------------+

mysql> status
--------------
mysql Ver 14.14 Distrib 5.1.73, for debian-linux-gnu (x86_64) using readline 5.1

Server version: 5.1.73-rel14.11 (Percona Server (GPL), 14.11, Revision 603)

[Shahriyar Rzayev (rzayev-sehriyar)]

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