Wrong my.cnf after resize revert

[Ed Cranford]

Reverting a resize after the new instance has the new my.cnf in place causes the original instance to hold onto the old my.cnf, because /etc/mysql/my.cnf is symlinked to a file in /var/lib, which is carried over when storage is disconnected from one and attached to the other instance.

What this means is you can potentially attempt to size an instance from half a gig to 2 gigs, have it fail, and then your original fails to start up because mysql can't get the resources asked for in the (wrong) my.cnf file.

We should deliberately revert the my.cnf as part of the revert process.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/31515

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/31515
Committed: http://github.com/openstack/trove/commit/2cb95d0f2b3f8cd44d24263af6d4a520a7ed02f5
Submitter: Jenkins
Branch: master

commit 2cb95d0f2b3f8cd44d24263af6d4a520a7ed02f5
Author: Ed Cranford <email address hidden>
Date: Mon Jun 17 14:52:49 2013 -0500

    Fixes my.cnf not reverting with a resize revert.

    Added GA method to fix db configurations without a restart.
    Revert resize now uses this method.

    Fixes Bug #1187028

    Change-Id: I2045d11c5a99ef26c1de297562a0a6239ca04789