yahoo-eng-team team mailing list archive

[OpenStack Infra <1618231@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/362468
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0f430425218859014fe2d10b9e618b29770c6581
Submitter: Jenkins
Branch:    master

commit 0f430425218859014fe2d10b9e618b29770c6581
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date:   Sat Aug 27 05:44:43 2016 -0700

    Generate new context for each DHCP RPC call
    
    The DHCP agent was using the same context for every RPC
    request so it made it difficult to tell server side where one
    RPC request began and where another one ended.
    
    This patch has it generate a new context for each RPC request
    so they can be tracked independently. In the long term it would
    be better if the agent kept the context for server-initiated events
    so actions could be tracked end-to-end under the same request-ID.
    
    Change-Id: I1d6dc28ba4752d3f9f1020851af2960859aae520
    Closes-Bug: #1618231


** 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/1618231

Title:
  dhcp agent uses same request ID for every request

Status in neutron:
  Fix Released

Bug description:
  The DHCP agent uses the same context and subsequently the same request
  ID for every request it makes to the Neutron server. This makes
  searching for single actions based on request ID very ineffective.

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