openstack team mailing list archive

[Blair Zajac <blair@xxxxxxxxxxxx>]

I've set up a new Folsom instance on an Ubuntu 12.10 system.  Trying to 
launch a new instance booting from a volume snapshot, which failed with 
the below stacktrace saying that nova-volumes cannot be found.  This 
suggests to me that nova is using nova-volumes instead of cinder, even 
though I've set up cinder with a LVM volume group named cinder-volumes:

# nova.con
volume_api_class=nova.volume.cinder.API
osapi_volume_listen_port=5900
# MAKE SURE NO ENTRY FOR osapi_volume anywhere in nova.conf!!!
# Leaving out enabled_apis altogether is NOT sufficient, as it defaults
# to include osapi_volume
enabled_apis=ec2,osapi_compute,metadata


# cinder.conf
volume_name_template = volume-%s
volume_group = cinder-volumes



Is this a known issue?  I've since set 'volume_group = cinder-volumes' 
but I'm guessing this shouldn't be necessary?

Blair



2013-01-21 22:44:21 DEBUG nova.utils 
[req-38df4209-f04f-4fe0-b0ab-14625a7eccba None None] Running cmd 
(subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf vgs 
--noheadings -o name from (pid=2841) execute /usr/
lib/python2.7/dist-packages/nova/utils.py:176
2013-01-21 22:44:24 DEBUG nova.utils 
[req-38df4209-f04f-4fe0-b0ab-14625a7eccba None None] Result was 0 from 
(pid=2841) execute /usr/lib/python2.7/dist-packages/nova/utils.py:191
2013-01-21 22:44:24 CRITICAL nova [-] Bad or unexpected response from 
the storage volume backend API: volume group nova-volumes doesn't exist
2013-01-21 22:44:24 TRACE nova Traceback (most recent call last):
2013-01-21 22:44:24 TRACE nova   File "/usr/bin/nova-volume", line 48, 
in <module>
2013-01-21 22:44:24 TRACE nova     service.wait()
2013-01-21 22:44:24 TRACE nova   File 
"/usr/lib/python2.7/dist-packages/nova/service.py", line 659, in wait
2013-01-21 22:44:24 TRACE nova     _launcher.wait()
2013-01-21 22:44:24 TRACE nova   File 
"/usr/lib/python2.7/dist-packages/nova/service.py", line 192, in wait
2013-01-21 22:44:24 TRACE nova     super(ServiceLauncher, self).wait()
2013-01-21 22:44:24 TRACE nova   File 
"/usr/lib/python2.7/dist-packages/nova/service.py", line 162, in wait
2013-01-21 22:44:24 TRACE nova     service.wait()
2013-01-21 22:44:24 TRACE nova   File 
"/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 166, in 
wait
2013-01-21 22:44:24 TRACE nova     return self._exit_event.wait()
2013-01-21 22:44:24 TRACE nova   File 
"/usr/lib/python2.7/dist-packages/eventlet/event.py", line 116, in wait
2013-01-21 22:44:24 TRACE nova     return hubs.get_hub().switch()
2013-01-21 22:44:24 TRACE nova   File 
"/usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 177, in switch
2013-01-21 22:44:24 TRACE nova     return self.greenlet.switch()
2013-01-21 22:44:24 TRACE nova   File 
"/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 192, in 
main
2013-01-21 22:44:24 TRACE nova     result = function(*args, **kwargs)
2013-01-21 22:44:24 TRACE nova   File 
"/usr/lib/python2.7/dist-packages/nova/service.py", line 132, in run_server
2013-01-21 22:44:24 TRACE nova     server.start()
2013-01-21 22:44:24 TRACE nova   File 
"/usr/lib/python2.7/dist-packages/nova/service.py", line 398, in start
2013-01-21 22:44:24 TRACE nova     self.manager.init_host()
2013-01-21 22:44:24 TRACE nova   File 
"/usr/lib/python2.7/dist-packages/nova/volume/manager.py", line 99, in 
init_host
2013-01-21 22:44:24 TRACE nova     self.driver.check_for_setup_error()
2013-01-21 22:44:24 TRACE nova   File 
"/usr/lib/python2.7/dist-packages/nova/volume/driver.py", line 115, in 
check_for_setup_error
2013-01-21 22:44:24 TRACE nova     raise 
exception.VolumeBackendAPIException(data=exception_message)
2013-01-21 22:44:24 TRACE nova VolumeBackendAPIException: Bad or 
unexpected response from the storage volume backend API: volume group 
nova-volumes doesn't exist