Unintentional change of innodb_version format in 5.1.60

Bug #917246 reported by Alexey Kopytov
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Ignacio Nin

Bug Description

https://code.launchpad.net/~percona-dev/percona-server/release-5.1.60-13.1/+merge/86334 has introduced a change in the innodb_version format. Previously, it was reported as "1.0.x-x.x". In 5.1.60 it is reported as "1.0.17-rel13.1".

That has broken XtraBackup automatic version detection, see XtraBackup bug #910206. I'm going to add a workaround to XtraBackup, but it would be good to have a consistent format for innodb_version.

Related branches

Changed in percona-server:
assignee: nobody → Ignacio Nin (ignacio-nin)
milestone: none → 5.1.61-13.2
status: New → Confirmed
description: updated
Changed in percona-server:
importance: Undecided → High
Changed in percona-server:
status: Confirmed → Fix Committed
Changed in percona-server:
status: Fix Committed → Fix Released
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-537

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

Other bug subscribers