spurious mysql root user created when deploying a HA control plane

Bug #1867165 reported by Damien Ciabrini
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Medium
Damien Ciabrini

Bug Description

When deploying a 3-node galera cluster, three mysql databases are created on each controller node. each database create various root users (root@%, root@localhost, root@<controller-x>).

The first time the galera cluster is started, the galera resource agent select a node to bootstrapped the cluster from. Currently this ends up selecting controller-2. The other two controllers synchronize the content of their DB to that of controller-2. This means root user root@controller-0 and root@controller-1 are destroyed in the process.

We never use root@controller-2 in tripleo, but this spurious user stays in the database anyway and should get dropped eventually.

summary: - spurious root user created when deploying a HA control planemysql
+ spurious mysql root user created when deploying a HA control plane
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (master)

Fix proposed to branch: master
Review: https://review.opendev.org/712726

Changed in tripleo:
assignee: nobody → Damien Ciabrini (dciabrin)
status: New → In Progress
Changed in tripleo:
importance: Undecided → Medium
milestone: none → ussuri-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (master)

Reviewed: https://review.opendev.org/712726
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=a67cfd0ba9b0900bc276c5c667dafe2824f54a47
Submitter: Zuul
Branch: master

commit a67cfd0ba9b0900bc276c5c667dafe2824f54a47
Author: Damien Ciabrini <email address hidden>
Date: Thu Mar 12 17:06:14 2020 +0100

    HA: drop spurious mysql user on stack deploy

    In HA deployments, puppet-mysql is not in charge of deleting
    all default users in the DB, so we end up keeping an extra
    root@<controller-x> user that is never used nor supported for
    password update. Make sure we delete it at creation time.

    Change-Id: I0dbe6bd43ad0e6bcb884798912d195e94738c344
    Closes-Bug: #1867165

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (stable/train)

Fix proposed to branch: stable/train
Review: https://review.opendev.org/715906

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (stable/train)

Reviewed: https://review.opendev.org/715906
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=e7a4cee7b92ff8119be34d750b08624b348d739f
Submitter: Zuul
Branch: stable/train

commit e7a4cee7b92ff8119be34d750b08624b348d739f
Author: Damien Ciabrini <email address hidden>
Date: Thu Mar 12 17:06:14 2020 +0100

    HA: drop spurious mysql user on stack deploy

    In HA deployments, puppet-mysql is not in charge of deleting
    all default users in the DB, so we end up keeping an extra
    root@<controller-x> user that is never used nor supported for
    password update. Make sure we delete it at creation time.

    Change-Id: I0dbe6bd43ad0e6bcb884798912d195e94738c344
    Closes-Bug: #1867165
    (cherry picked from commit a67cfd0ba9b0900bc276c5c667dafe2824f54a47)

tags: added: in-stable-train
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 12.2.0

This issue was fixed in the openstack/tripleo-heat-templates 12.2.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 11.4.0

This issue was fixed in the openstack/tripleo-heat-templates 11.4.0 release.

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

Other bug subscribers

Remote bug watches

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