yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #11304
[Bug 1284456] Re: libvirt_inject_partition -2 instances fail to spawn
After further investigation libguestfs was not installed which caused
nova-compute to hang as stated in bug description.
Move to 2013.2.2 , nova no longer hangs if libguestfs is not installed
but still throws errors in nova-compute :
sudo nova-rootwrap /etc/nova/rootwrap.conf mount /dev/nbd7 /tmp/openstack-vfs-localfsPfAFxU
Exit code: 32
Stdout: ''
Stderr: 'mount: you must specify the filesystem type\n'.
Cannot resize. is_image_partitionless /usr/lib/python2.7/dist-packages/nova/virt/disk/api.py:183
Closing as not a bug.
** Changed in: nova
Status: New => Invalid
--
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/1284456
Title:
libvirt_inject_partition -2 instances fail to spawn
Status in OpenStack Compute (Nova):
Invalid
Bug description:
Using 2013.2.1 from Ubuntu packages.
I want prevent libvirt from injecting anything in to any image so I
set:
libvirt_inject_partition = -2 in nova.conf
Then proceed to launch and instances (cirros).
I still see nova trying to mount the instances disk. Why?
sudo nova-rootwrap /etc/nova/rootwrap.conf mount /dev/nbd7 /tmp/openstack-vfs-localfsPfAFxU
Exit code: 32
Stdout: ''
Stderr: 'mount: you must specify the filesystem type\n'.
Cannot resize. is_image_partitionless /usr/lib/python2.7/dist-packages/nova/virt/disk/api.py:183
The instance goes in spawning state forever and running nova-manage
service-list I can see my HV is now disconnected:
nova-compute hv10 nova
enabled XXX 2014-02-25 04:47:29
On the HV:
service nova-compute status
nova-compute start/running, process 23144
ps -ef | grep -i nova :
nova 23144 1 0 20:38 ? 00:00:04 /usr/bin/python /usr/bin/nova-compute --config-file=/etc/nova/nova.conf --config-file=/etc/nova/nova-compute.conf
So compute is running but no longer sending any updates.
No trace back in the logs.
Last message in the logs is :
Stderr: 'mount: you must specify the filesystem type\n'. Cannot resize. is_image_partitionless /usr/lib/python2.7/dist-packages/nova/virt/disk/api.py:183
2014-02-24 20:47:20.429 23144 DEBUG nova.openstack.common.lockutils [req-a155702e-dc1e-460d-ad3e-d2998c9afe0f d83a0210b9da4f6b94d9e13a23dafddb a934178896aa4b508d4b05628e26b1d9] Released file lock "/var/lib/nova/instances/_base/5458981acff074f9b700e996269524da9bad856c" at /var/lib/nova/instances/locks/nova-_var_lib_nova_instances__base_5458981acff074f9b700e996269524da9bad856c lock /usr/lib/python2.7/dist-packages/nova/openstack/common/lockutils.py:208
Restarting nova-compute brings the HV back to life:
nova-compute hv10 nova
enabled :-) 2014-02-25 05:15:22
This is reproducible 100% on my setup with multiple compute nodes.
Thanks..
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1284456/+subscriptions
References