LBaaS V2 Octavia driver should create get its own context/session

Bug #1497823 reported by Brandon Logan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Undecided
Brandon Logan

Bug Description

The LBaaS V2 Octavia driver currently uses the context that is passed from the plugin. Since the driver spins up a thread to poll Octavia, each thread should create its own context.

Tags: lbaas
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron-lbaas (master)

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

Changed in neutron:
assignee: nobody → Brandon Logan (brandon-logan)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron-lbaas (master)

Reviewed: https://review.openstack.org/225542
Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=a3a3531aff2bd830d740fd8418011eaa3dc4a831
Submitter: Jenkins
Branch: master

commit a3a3531aff2bd830d740fd8418011eaa3dc4a831
Author: Brandon Logan <email address hidden>
Date: Sun Sep 20 22:41:16 2015 -0500

    Use admin context in octavia driver, improve logs

    When polling for the status of a load balancer in octavia, the context created
    by the plugin was being used. Since the polling takes place in a thread, that
    context can have some unexpected behavior. It is better to create an admin
    context in the thread because it definitely exists in that thread.

    Also improve debug logging in the octavia driver and the successful and failed
    completion helper methods in the mixins.

    Change-Id: I6f64c95d89876c9d1d19076a4fe7e3006a0df5e0
    Closes-Bug: #1497823

Changed in neutron:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in neutron:
milestone: none → liberty-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: liberty-rc1 → 7.0.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.