yahoo-eng-team team mailing list archive

[Christian Berendt <1280357@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When using a weak storage backend and initiating the creation of a lot
of new instances using volumes as backend (directly created from an
image) I got a lot of InvalidBDM: Block Device Mapping is Invalid. After
I had a look on the method _await_block_device_map_created (in
nova/manager/ComputeManager) the solution was pretty easy: increasing
the max_tries and/or wait_between parameters solved the issue. The
storage backend could simply not provide this mass of volumes in a very
short time (100 seconds on my testing system).

** 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/1280357

Title:
  parameters max_tries and wait_between of method
  ComputeManager._await_block_device_map_created should be configurable

Status in OpenStack Compute (Nova):
  New

Bug description:
  When using a weak storage backend and initiating the creation of a lot
  of new instances using volumes as backend (directly created from an
  image) I got a lot of InvalidBDM: Block Device Mapping is Invalid.
  After I had a look on the method _await_block_device_map_created (in
  nova/manager/ComputeManager) the solution was pretty easy: increasing
  the max_tries and/or wait_between parameters solved the issue. The
  storage backend could simply not provide this mass of volumes in a
  very short time (100 seconds on my testing system).

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