Ask Your Question
0

VolumeNotCreated: Volume did not finish being created even after we waited 197 seconds or 61 attempts

asked 2017-05-03 10:59:07 -0500

bertly gravatar image

Hi, currently running in the following error while creating a new server. Cinder is very slow (which is atm okay) and nova-compute stops waiting for the image to be created.

Where can I configure this timeouts? I can't find it in the documentation of Openstack Newton.

2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [req-cf72b121-a4f8-40a5-b235-38cabc8a508f 217ce8c543b3495fa23b48a99cf9e4c5 3723cf7355e946efbf40f4f29ff845f6 - - -] [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f] Instance failed block device setup
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f] Traceback (most recent call last):
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1586, in _prep_block_device
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]     wait_func=self._await_block_device_map_created)
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]   File "/usr/lib/python2.7/dist-packages/nova/virt/block_device.py", line 514, in attach_block_devices
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]     map(_log_and_attach, block_device_mapping)
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]   File "/usr/lib/python2.7/dist-packages/nova/virt/block_device.py", line 512, in _log_and_attach
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]     bdm.attach(*attach_args, **attach_kwargs)
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]   File "/usr/lib/python2.7/dist-packages/nova/virt/block_device.py", line 404, in attach
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]     self._call_wait_func(context, wait_func, volume_api, vol['id'])
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]   File "/usr/lib/python2.7/dist-packages/nova/virt/block_device.py", line 363, in _call_wait_func
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]     {'volume_id': volume_id, 'exc': exc})
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]   File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]     self.force_reraise()
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]   File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]     six.reraise(self.type_, self.value, self.tb)
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]   File "/usr/lib/python2.7/dist-packages/nova/virt/block_device.py", line 353, in _call_wait_func
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]     wait_func(context, volume_id)
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1258, in _await_block_device_map_created
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f]     volume_status=volume_status)
2017-05-03 17:55:18.229 30849 ERROR nova.compute.manager [instance: 0e4680eb-fe6a-4573-bbc4-84bdf27e879f] VolumeNotCreated: Volume 159efd05-b301-4994-b76d-4fd92695e876 did not finish being created even after we waited 197 seconds or 61 attempts. And its status is creating.
2017-05-03 17:55:18.229 30849 ...
(more)
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
3

answered 2017-05-03 11:11:53 -0500

The config parameter you are looking for is block_device_allocate_retries. The default is 60 - which matches your scenario.

edit flag offensive delete link more

Comments

yes thats it. Thank you.

bertly gravatar imagebertly ( 2017-05-04 02:26:41 -0500 )edit

Thanks, helped me further as well. Increased the same setting to allocate volumes faster on our attached SAN storage

fattony666 gravatar imagefattony666 ( 2018-04-12 03:19:05 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-05-03 10:59:07 -0500

Seen: 6,319 times

Last updated: May 03 '17