networking-hyperv

Logs spam generated by locks

Bug #1744751 reported by Claudiu Belu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-hyperv
Fix Released
Wishlist
Claudiu Belu

Bug Description

The Hyper-V Neutron Agent is configured by default to run a loop every 2 seconds. In this loop, a lock is aquired in order to avoid some race conditions. A new log entry is added each time the lock is aquired / released (if debug is enabled).

This can make debugging more difficult.

Logs: paste.openstack.org/show/650087/

See original description
Claudiu Belu (cbelu)
Changed in networking-hyperv:
importance: Undecided → Wishlist
assignee: nobody → Claudiu Belu (cbelu)
status: New → Confirmed
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-hyperv (master)

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

Changed in networking-hyperv:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-hyperv (master)

Reviewed: https://review.openstack.org/537804
Committed: https://git.openstack.org/cgit/openstack/networking-hyperv/commit/?id=72c0fc3c3f474ea7ae59619c5559d9db0212636f
Submitter: Zuul
Branch: master

commit 72c0fc3c3f474ea7ae59619c5559d9db0212636f
Author: Claudiu Belu <email address hidden>
Date: Thu Jan 25 10:38:08 2018 +0200

    Avoids unnecessary lock logging every loop

    _notify_plugin_on_port_updates is called every loop (default - every
    2 seconds), and since it has a lock, every lock aquire / release gets
    logged if the debug mode is set to True. This can generate a lot of
    useless logs, which will make debugging more difficult.

    Change-Id: I29045da42ba03209241cc36e3cf0052ed690afc8
    Closes-Bug: #1744751

Changed in networking-hyperv:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-hyperv 6.0.0

This issue was fixed in the openstack/networking-hyperv 6.0.0 release.

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.