← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1367941] Re: Able to aquire the semaphore used in lockutils.synchronized_with_prefix twice at the same time

 

** Also affects: oslo.concurrency
   Importance: Undecided
       Status: New

** Changed in: oslo.concurrency
       Status: New => Triaged

** Changed in: oslo.concurrency
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1367941

Title:
  Able to aquire the semaphore used in
  lockutils.synchronized_with_prefix twice at the same time

Status in OpenStack Compute (Nova):
  Confirmed
Status in The Oslo library incubator:
  Confirmed
Status in Oslo Concurrency Library:
  Triaged

Bug description:
  In nova-compute the semaphore "compute_resources" is used  in
  lockutils.synchronized_with_prefix('nova-') as part of
  nova/compute/resource_tracker.py

  The "compute_resources"  semaphore is acquired once at:

  http://logs.openstack.org/58/117258/2/gate/gate-tempest-dsvm-neutron-
  full/48c8627/logs/screen-n-cpu.txt.gz?#_2014-09-10_20_19_17_176

  And then again at:

  In  http://logs.openstack.org/58/117258/2/gate/gate-tempest-dsvm-
  neutron-
  full/48c8627/logs/screen-n-cpu.txt.gz?#_2014-09-10_20_19_52_234

  without being released in between.  This means
  lockutils.synchronized_with_prefix('nova-') isn't working as expected.

  While https://review.openstack.org/#/c/119586/ is a possible culprit
  for this issue, a spot check of nova-compute logs from before that
  patch was merged show this was happening before (although in my spot
  checking it happened significantly less often, but I only checked one
  file).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1367941/+subscriptions


References