Designate

Pool Manager should reuse the existing threadgroup

Bug #1412590 reported by Kiall Mac Innes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
Fix Released
High
Kiall Mac Innes
Designate 2015.1.0 "kilo"

Bug Description

Pool Manager should reuse the existing threadgroup provided by the base service class

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to designate (master)

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

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

Reviewed: https://review.openstack.org/148375
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=a50362766d5cfd54b995e33f306475b115c92b29
Submitter: Jenkins
Branch: master

commit a50362766d5cfd54b995e33f306475b115c92b29
Author: Kiall Mac Innes <email address hidden>
Date: Mon Jan 19 14:33:02 2015 -0800

    Pool Manager should reuse the existing threadgroup

    The base Service class provides a thread gtroup at self.tg,
    we should reuse this rather than create a new one.

    Change-Id: I49c23596dc5dd47cf75d83b0089c052fc486368c
    Closes-Bug: 1412590

Changed in designate:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in designate:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in designate:
milestone: kilo-2 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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