Public bug reported:
[Impact]
User tried a ceph storage node intentionally degraded, as a failure test case,
on all the cases we hit
the following exception,
2014-07-07 04:07:01.121 1573 TRACE nova.compute.manager [instance:
63386638-58ac-4a2d-ae3a-20ecc137c5ad] VolumeNotCreated: Volume 4b6611e2
-0e6b-44ec-8066-f8ac164d6a9c did not finish being created even after we
waited 197 seconds or 180 attempts.
2014-07-07 04:07:01.121 1573 TRACE nova.compute.manager [instance:
63386638-58ac-4a2d-ae3a-20ecc137c5ad]
2014-07-07 04:07:01.750 1573 ERROR oslo.messaging.rpc.dispatcher [-] Exception
during message handling: Block Device Mapping is Invalid.
This change adds two configuration options:
a) `block_device_allocate_retries` which can be set in nova.conf
by the user to configure the number of block device mapping retries.
It defaults to 60 and replaces the max_tries argument in the above method.
b) `block_device_allocate_retries_interval` which allows the user
to specify the time interval between consecutive retries. It defaults to 3
and replaces wait_between argument in the above method.
[Regression Potential]
* This change introduces two new nova.conf directives, both with
default values that shouldn't broken previous deployments.
[Other Info]
Please refer upstream commit:
https://git.openstack.org/cgit/openstack/nova/commit/?id=66721eb2c0f53fc4260b2f0aa9a3811da0f7ddbd
** Affects: nova (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376927
Title:
[SRU] Configurable block device mapping timeout in compute
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1376927/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
