usage_timeout option still remain as the part of the per-datastore groups

Bug #1361603 reported by Denis M.
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
Medium
Amrith Kumar
Denis M. (dmakogon)
Changed in trove:
importance: Undecided → Medium
milestone: none → juno-3
Revision history for this message
Amrith Kumar (amrith) wrote :

Assigning to myself because I made the last commit in this area just recently (merged yesterday).

Changed in trove:
assignee: nobody → Amrith (amrith)
Denis M. (dmakogon)
Changed in trove:
status: New → In Progress
Revision history for this message
Greg Lucas (glucas-q) wrote :

Since it wasn't clear to me until I went digging in to history, this bug relates to:

blueprint refactoring-datastore-options-in-cfg
Change-Id: I3b4b2a9bffb40df4531a78c29d1e155e59436948

Changed in trove:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in trove:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in trove:
milestone: juno-3 → 2014.2
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.