neutron

dhcp agent uses same request ID for every request

Bug #1618231 reported by Kevin Benton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Low
Kevin Benton

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.

Kevin Benton (kevinbenton)
Changed in neutron:
assignee: nobody → Kevin Benton (kevinbenton)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

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

Changed in neutron:
status: New → In Progress
Dariusz Smigiel (smigiel-dariusz)
Changed in neutron:
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

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 <email address hidden>
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
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 9.0.0.0b3

This issue was fixed in the openstack/neutron 9.0.0.0b3 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to neutron (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/364634

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to neutron (master)

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

commit c7369483557e23782d2ec293d548bc96cd729934
Author: Kevin Benton <email address hidden>
Date: Thu Sep 1 20:07:09 2016 -0700

    Make L3 agent use different request-id for each request

    Generate a new context object request-id for each reference
    to self.context. This allows easier tracking of requests
    in logs.

    This is the L3 agent equivalent fix of
    I1d6dc28ba4752d3f9f1020851af2960859aae520.

    Related-Bug: #1618231
    Closes-Bug: #1619524
    Change-Id: I4a49f05ce0e7467084a1c27a64a0d4cf60a5f8cb

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.