Move MySQL ignore_users and other configuration options into the MySQL section from default.

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

Bug Description

MySQL datastore specific configuration options like ignore_users are still part of default. Move them to the MySQL section.

Changed in trove:
milestone: liberty-1 → liberty-2
Changed in trove:
status: New → Triaged
Changed in trove:
milestone: liberty-2 → liberty-3
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/207833

Changed in trove:
status: Triaged → In Progress
Changed in trove:
milestone: liberty-3 → ongoing
Changed in trove:
milestone: ongoing → liberty-rc1
Revision history for this message
Nikhil Manchanda (slicknik) wrote :

This is "good to have" but not blocking Liberty RC1. Moving to Mitaka based on this.

Changed in trove:
milestone: liberty-rc1 → mitaka-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (master)

Reviewed: https://review.openstack.org/207833
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=9f07d7da8dcb0c9162be479a6587f352c37f9024
Submitter: Jenkins
Branch: master

commit 9f07d7da8dcb0c9162be479a6587f352c37f9024
Author: Amrith Kumar <email address hidden>
Date: Mon Sep 14 18:32:48 2015 +0000

    Move ignore_dbs and ignore_users out of DEFAULT

    ignore_dbs and ignore_users (for MySQL) were still in DEFAULT section
    of config. Moved them to the 'mysql' section and 'percona'
    section. Sample config file(s) have been updated as well.

    Change-Id: I3a41bcb011a76343afa3bcc30013cb835e456950
    Closes-Bug: #1465242
    Closes-Bug: #1480448
    Closes-Bug: #1480447
    Closes-Bug: #1374004

Changed in trove:
status: In Progress → Fix Committed
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/trove 5.0.0.0b1

This issue was fixed in the openstack/trove 5.0.0.0b1 development milestone.

Changed in trove:
status: Fix Committed → Fix Released
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.