Closed Bug 892987 Opened 11 years ago Closed 11 years ago

Upgrade to MySQL 5.6 on engagement dev/stage

Categories

(Data & BI Services Team :: DB: MySQL, task)

Product:
Data & BI Services Team
Component:
DB: MySQL
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: scabral, Unassigned)

Details

We need to upgrade to MySQL 5.6 on:

node36
node37
node38
node39
Doing node36 and node38 in parallel with these steps:

removed packages with yum:
manually installed MySQL 5.6 packages (manual until the puppet packages are put in place)

Re-installed percona toolkit

Ran puppet

Make sure /etc/my.cnf exists and wasn't moved to my.cnf.rpmsave

Start mysql

Run mysql_upgrade

Check to see that the slave is running fine

Disable puppet with:
 /usr/local/sbin/puppetctl  disable -t 'now + 6 days' -m 'Disabled while waiting for packages to be put into puppet'

addons5.stage is now upgraded.
upgrading node37 now.
node37 upgraded, node39 upgrade in progress.
node39 upgrade complete. all machines are back in the load balancer.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Data & BI Services Team
You need to log in before you can comment on or make changes to this bug.