yahoo-eng-team team mailing list archive

[OpenStack Infra <1641788@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/397497
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7c7e2418a238d53042b1b30fefe9aea05cf02681
Submitter: Jenkins
Branch:    master

commit 7c7e2418a238d53042b1b30fefe9aea05cf02681
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date:   Mon Nov 14 17:53:30 2016 -0800

    Fix reset/start methods on AgentStatusCheckWorker
    
    This worker would fail to start again if stop() or reset()
    was called on it because of some bad conditional logic. This
    doesn't appear to impact the current in-tree use case but
    it should behave correctly.
    
    Closes-Bug: #1641788
    Change-Id: Id6334c1ef6c99bd112ada31e8fe3746d7e035356


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1641788

Title:
  AgentStatusCheckWorker doesn't reset or start after stop

Status in neutron:
  Fix Released

Bug description:
  The AgentStatusCheckWorker we have in tree doesn't correctly recover
  if the .stop() or .reset() methods are called to it due to some bad
  conditionals. This doesn't currently impact the in-tree use-case since
  we don't stop and restart the status checkers, but it should be fixed
  so it can be safely re-used elsewhere for periodic workers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1641788/+subscriptions