l3 agent uses same request ID for every request

[Kevin Benton]

The L3 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.

DHCP version of this bug is here: https://bugs.launchpad.net/neutron/+bug/1618231

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 9.0.0.0rc1 release candidate.