Percona Server moved to https://jira.percona.com/projects/PS

Slave broken after Percona 5.6 upgrade

Bug #1156997 reported by Alexey Kopytov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Expired
Undecided
Unassigned

Bug Description

Converting https://answers.launchpad.net/percona-server/+question/224153 to a bug report for further analysis:

"
Hi,

We were in a process of testing Percona 5.6 upgrade in our test environment but after upgrade (from percona 5.5), I could find that the slave is broken after the upgrade and slave status shows empty results. The steps we have followed is :

1) Stopped slave and Mysql
2) Uninstalled the 5.5 and installed the percona 5.6 using rpm
3) Started the Mysql and run the upgrade

Please advice if we did something wrong..

Thank you,
Austin
"

Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

Please, provide additional information as requested in the original question, https://answers.launchpad.net/percona-server/+question/224153

Changed in percona-server:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Percona Server because there has been no activity for 60 days.]

Changed in percona-server:
status: Incomplete → Expired
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-2916

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

Other bug subscribers

Related questions

Remote bug watches

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