yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => icehouse-3

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

Title:
  cache lock for image not consistent

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  According to this bug https://bugs.launchpad.net/nova/+bug/1256306

  for one image in _base dir 03d8e206-6500-4d91-b47d-ee74897f9b4e
  2 locks were created 

  -rw-r--r-- 1 nova nova 0 Oct 4 20:40 nova-03d8e206-6500-4d91-b47d-
  ee74897f9b4e

  -rw-r--r-- 1 nova nova 0 Oct 4 20:40 nova-
  _var_lib_nova_instances__base_03d8e206-6500-4d91-b47d-ee74897f9b4e

  generally locks are used to protect concurrent data access, so the lock can't work as they expected (mutual access)
  in current code fetch_image from glance use lock nova-xxxxx while copy image from _base to target directory use nova_var_lib_xxx
  should they use same lock?

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