Juno -> Kilo upgrade script LB galera monitoring user issues

[Andy McCrae]

The LB monitoring user changed from "haproxy" to "montoring" by default.
The haproxy user is removed from mysql (although not entirely since it exists as haproxy@localhost still), this creates an issue though - the user is removed at the very beginning of the upgrade, but the new user isn't created until the mysql play happens (quite a long time later).

During this time the OpenStack cluster is effectively unavailable since galera is unavailable.

During the upgrade we should create the new user as we remove the old user to avoid this happening.

[Jesse Pretorius (jesse-pretorius)]

review: https://review.openstack.org/228983

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/228983
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=f720fd7821ef9bd03bd9d9e8a51488c94b6ec7fe
Submitter: Jenkins
Branch: kilo

commit f720fd7821ef9bd03bd9d9e8a51488c94b6ec7fe
Author: Andy McCrae <email address hidden>
Date: Tue Sep 29 15:49:00 2015 +0100

    Add galera monitoring user during upgrades

    We changed the default galera_monitoring_user from "haproxy" to
    "monitoring".

    This patch ensures the old "haproxy" user is fully cleaned up
    (previously only 'haproxy'@'%' was removed, leaving
    'haproxy'@'localhost' in place.)
    This patch adds the new monitoring user to avoid downtime on the galera
    VIP during the upgrade - which happens because the monitor fails now
    that the monitoring user has been removed/changed.

    Change-Id: I07d753d51a5b2770064a26bdcf1cbaa4853ab49b
    Closes-bug: #1500911

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.