L3 agent driver singletons pointing at old agent during testing

[Assaf Muller]

L3 agent drivers are singletons. They're created once, and hold self.l3_agent. During testing, the agent is tossed away and re-built, but the drivers singletons are pointing at the old agent, and its old configuration. Single each agent has its own state_path (And dependent metadata_proxy_socket and such), the drivers are looking at old, non-relevant configuration.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit 1e562decdc03295dec4cb37d26162e5d9aa31079
Author: Assaf Muller <email address hidden>
Date: Sun Dec 21 16:15:12 2014 +0200

    Update L3 agent drivers singletons to look at new agent

    L3 agent drivers are singletons. They're created once, and hold
    self.l3_agent. During testing, the agent is tossed away and
    re-built, but the drivers singletons are pointing at the old
    agent, and its old configuration.

    Change-Id: Ie8a15318e71ea47cccad3b788751d914d51cbf18
    Closes-Bug: #1404662