OpenStack Compute (nova)

  1. Bug #1367941
  2. Comment #10

Comment 10 for bug 1367941

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :

So, with the updates to the logging, i am looking at
http://logs.openstack.org/34/120934/1/check/check-tempest-dsvm-neutron-full/4c35ad6/logs/screen-n-cpu.txt.gz

I can see 2 Acquired one after another w/o a Releasing

2014-09-11 23:50:26.641 31439 DEBUG nova.openstack.common.lockutils Acquired semaphore "compute_resources" lock /opt/stack/new/nova/nova/openstack/common/lockutils.py:229
2014-09-11 23:51:10.473 DEBUG nova.openstack.common.lockutils Using existing semaphore "compute_resources" internal_lock /opt/stack/new/nova/nova/openstack/common/lockutils.py:202
2014-09-11 23:51:37.804 DEBUG nova.openstack.common.lockutils Acquired semaphore "compute_resources" lock /opt/stack/new/nova/nova/openstack/common/lockutils.py:229
2014-09-11 23:51:37.830 DEBUG nova.openstack.common.lockutils Releasing semaphore "compute_resources" lock /opt/stack/new/nova/nova/openstack/common/lockutils.py:236