yahoo-eng-team team mailing list archive

[Doug Hellmann <doug@xxxxxxxxxxxxxxxx>]

Public bug reported:

It's not clear if n-cpu is dying trying to acquire the lock
"lock_bridge" or if it's just hanging.

http://logs.openstack.org/08/109108/1/check/check-tempest-dsvm-
full/4417111/logs/screen-n-cpu.txt.gz

The logs for n-cpu stop about 15 minutes before the rest of the test
run, and all tests doing things that require the hypervisor executed
after that point fail with different errors.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1349452

Title:
  apparent deadlock on lock_bridge in n-cpu

Status in OpenStack Compute (Nova):
  New

Bug description:
  It's not clear if n-cpu is dying trying to acquire the lock
  "lock_bridge" or if it's just hanging.

  http://logs.openstack.org/08/109108/1/check/check-tempest-dsvm-
  full/4417111/logs/screen-n-cpu.txt.gz

  The logs for n-cpu stop about 15 minutes before the rest of the test
  run, and all tests doing things that require the hypervisor executed
  after that point fail with different errors.

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