Public bug reported:
The resize_fs_using_block_device config option allows to configure if a
filesystem within an image is resized by nova during spawn or not. When
it's set to False (which is the default) nova still tries to access the
image to find out if it's extendable or not, although it's not resized
afterwards.
On system which don't have libguestfs or nbd installed, this causes the
following error messages repeatedly:
2015-03-30 16:49:40.326 ERROR nova.virt.disk.mount.nbd
[req-3d3c5a50-6067-442a-9607-1f98141d795c None None] nbd module not loaded
2015-03-30 16:49:40.327 INFO nova.virt.disk.mount.api
[req-3d3c5a50-6067-442a-9607-1f98141d795c None None] Device allocation failed.
Will retry in 2 seconds.
2015-03-30 16:49:42.329 ERROR nova.virt.disk.mount.nbd
[req-3d3c5a50-6067-442a-9607-1f98141d795c None None] nbd module not loaded
2015-03-30 16:49:42.330 INFO nova.virt.disk.mount.api
[req-3d3c5a50-6067-442a-9607-1f98141d795c None None] Device allocation failed.
Will retry in 2 seconds.
2015-03-30 16:49:44.332 ERROR nova.virt.disk.mount.nbd
[req-3d3c5a50-6067-442a-9607-1f98141d795c None None] nbd module not loaded
2015-03-30 16:49:44.333 INFO nova.virt.disk.mount.api
[req-3d3c5a50-6067-442a-9607-1f98141d795c None None] Device allocation failed.
Will retry in 2 seconds.
So the instance spawn takes longer than necessary (retries are done for
~30 seconds).
I'll provide a patch to make sure the image is not accessed when
resizing is disabled.
** 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/1438245
Title:
Nova accesses image for resize even when resize is disabled
Status in OpenStack Compute (Nova):
New
Bug description:
The resize_fs_using_block_device config option allows to configure if
a filesystem within an image is resized by nova during spawn or not.
When it's set to False (which is the default) nova still tries to
access the image to find out if it's extendable or not, although it's
not resized afterwards.
On system which don't have libguestfs or nbd installed, this causes
the following error messages repeatedly:
2015-03-30 16:49:40.326 ERROR nova.virt.disk.mount.nbd
[req-3d3c5a50-6067-442a-9607-1f98141d795c None None] nbd module not loaded
2015-03-30 16:49:40.327 INFO nova.virt.disk.mount.api
[req-3d3c5a50-6067-442a-9607-1f98141d795c None None] Device allocation failed.
Will retry in 2 seconds.
2015-03-30 16:49:42.329 ERROR nova.virt.disk.mount.nbd
[req-3d3c5a50-6067-442a-9607-1f98141d795c None None] nbd module not loaded
2015-03-30 16:49:42.330 INFO nova.virt.disk.mount.api
[req-3d3c5a50-6067-442a-9607-1f98141d795c None None] Device allocation failed.
Will retry in 2 seconds.
2015-03-30 16:49:44.332 ERROR nova.virt.disk.mount.nbd
[req-3d3c5a50-6067-442a-9607-1f98141d795c None None] nbd module not loaded
2015-03-30 16:49:44.333 INFO nova.virt.disk.mount.api
[req-3d3c5a50-6067-442a-9607-1f98141d795c None None] Device allocation failed.
Will retry in 2 seconds.
So the instance spawn takes longer than necessary (retries are done
for ~30 seconds).
I'll provide a patch to make sure the image is not accessed when
resizing is disabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1438245/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
