PXC has a different secure method - this should be collapsed into the base 'mysql' secure

Bug #1585355 reported by Peter Stachowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
Medium
Peter Stachowski

Bug Description

When PXC was implemented, the secure method was overridden as the stock one was causing problems on prepare. This issue should be sorted out and PXC reverted to the base MySQL implementation. The relevant info seems to be:

 # creating the admin user after the config files are written because
 # percona pxc was not commiting the grant for the admin user after
 # removing the annon users.

Fix: create the admin user first and then use it to delete the anon users.

Changed in trove:
assignee: nobody → Peter Stachowski (peterstac)
milestone: none → newton-1
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

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

Changed in trove:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (master)

Reviewed: https://review.openstack.org/320697
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=0eb332ae8af2d55668ef3871295f59eff74b3edc
Submitter: Jenkins
Branch: master

commit 0eb332ae8af2d55668ef3871295f59eff74b3edc
Author: Peter Stachowski <email address hidden>
Date: Tue May 24 16:43:15 2016 -0400

    Fix secure method to work with PXC

    When PXC was implemented, the secure method was overridden as the
    stock one was causing problems on prepare. This issue seems to
    be caused by the order of work done in the call. If the admin
    user is set up first and then used to delete the anon users,
    everything works for all flavors of MySQL.

    Tested using the scenario tests on MySQL, Percona, PXC and MariaDB.

    Also cleaned up some of the common code and made the connection URL
    more resilient to special password characters. Updated the 'supported'
    tests and fixed the user actions one to work with PXC.

    Change-Id: Idf9a096b8870e428090454528b79930f3d2fd760
    Closes-Bug: #1585355

Changed in trove:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/trove 6.0.0.0b3

This issue was fixed in the openstack/trove 6.0.0.0b3 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

This issue was fixed in the openstack/trove 6.0.0.0b3 development milestone.

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.