Nova Volume Worker fails to start - error volume group nova-volumes does not exist

Asked by Rob Neff

I'm trying to setup an OpenStack Cloud Controller on RHEL6.1, and Nova Volume Worker fails to start.

[root@cloudsrest4 Documents]# sudo ./StartNovaServices.sh
nova-api is already running (pid 3148) [PASSED]
Starting OpenStack Nova Compute Worker: [ OK ]
Starting OpenStack Nova Network Controller: [ OK ]
nova-objectstore is already running (pid 3217) [PASSED]
nova-scheduler is already running (pid 8716) [PASSED]
Starting OpenStack Nova Volume Worker: [FAILED]

Command:
sudo service openstack-nova-volume start

Installed from:
openstack-repo-2011.3-0.2.noarch.rpm

OS:
RHEL6.1

Log:
2011-09-29 19:54:42,043 nova: Starting volume node (version 2011.3-nova-milestone-tarball:tarmac-20110825234031-sqwfb0kwnj0aw26t)
2011-09-29 19:54:42,043 nova.utils: Running cmd (subprocess): sudo vgs --noheadings -o name
2011-09-29 19:54:42,179 nova: volume group nova-volumes doesn't exist
(nova): TRACE: Traceback (most recent call last):
(nova): TRACE: File "/usr/bin/nova-volume", line 48, in <module>
(nova): TRACE: service.wait()
(nova): TRACE: File "/usr/lib/python2.6/site-packages/nova/service.py", line 367, in wait
(nova): TRACE: _launcher.wait()
(nova): TRACE: File "/usr/lib/python2.6/site-packages/nova/service.py", line 107, in wait
(nova): TRACE: service.wait()
(nova): TRACE: File "/usr/lib/python2.6/site-packages/eventlet/greenthread.py", line 166, in wait
(nova): TRACE: return self._exit_event.wait()
(nova): TRACE: File "/usr/lib/python2.6/site-packages/eventlet/event.py", line 116, in wait
(nova): TRACE: return hubs.get_hub().switch()
(nova): TRACE: File "/usr/lib/python2.6/site-packages/eventlet/hubs/hub.py", line 177, in switch
(nova): TRACE: return self.greenlet.switch()
(nova): TRACE: File "/usr/lib/python2.6/site-packages/eventlet/greenthread.py", line 192, in main
(nova): TRACE: result = function(*args, **kwargs)
(nova): TRACE: File "/usr/lib/python2.6/site-packages/nova/service.py", line 77, in run_server
(nova): TRACE: server.start()
(nova): TRACE: File "/usr/lib/python2.6/site-packages/nova/service.py", line 137, in start
(nova): TRACE: self.manager.init_host()
(nova): TRACE: File "/usr/lib/python2.6/site-packages/nova/volume/manager.py", line 81, in init_host
(nova): TRACE: self.driver.check_for_setup_error()
(nova): TRACE: File "/usr/lib/python2.6/site-packages/nova/volume/driver.py", line 92, in check_for_setup_error
(nova): TRACE: % FLAGS.volume_group)
(nova): TRACE: Error: volume group nova-volumes doesn't exist
(nova): TRACE:

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Rob Neff
Solved:
Last query:
Last reply:
Revision history for this message
Vish Ishaya (vishvananda) said :
#1

Nova does not attempt to create volume groups for the user. To use nova volume, you must either a) create a volume group called nova-volumes or b) specify a different volume group for volumes via the flag --volume_group=XXX where XXX is some other volume group with free space.

On Sep 29, 2011, at 1:10 PM, Rob Neff wrote:

> New question #172752 on OpenStack Compute (nova):
> https://answers.launchpad.net/nova/+question/172752
>
> I'm trying to setup an OpenStack Cloud Controller, and Nova Volume Worker fails to start.
>
> [root@cloudsrest4 Documents]# sudo ./StartNovaServices.sh
> nova-api is already running (pid 3148) [PASSED]
> Starting OpenStack Nova Compute Worker: [ OK ]
> Starting OpenStack Nova Network Controller: [ OK ]
> nova-objectstore is already running (pid 3217) [PASSED]
> nova-scheduler is already running (pid 8716) [PASSED]
> Starting OpenStack Nova Volume Worker: [FAILED]
>
> Command:
> sudo service openstack-nova-volume start
>
> Installed from:
> openstack-repo-2011.3-0.2.noarch.rpm
>
> Log:
> 2011-09-29 19:54:42,043 nova: Starting volume node (version 2011.3-nova-milestone-tarball:tarmac-20110825234031-sqwfb0kwnj0aw26t)
> 2011-09-29 19:54:42,043 nova.utils: Running cmd (subprocess): sudo vgs --noheadings -o name
> 2011-09-29 19:54:42,179 nova: volume group nova-volumes doesn't exist
> (nova): TRACE: Traceback (most recent call last):
> (nova): TRACE: File "/usr/bin/nova-volume", line 48, in <module>
> (nova): TRACE: service.wait()
> (nova): TRACE: File "/usr/lib/python2.6/site-packages/nova/service.py", line 367, in wait
> (nova): TRACE: _launcher.wait()
> (nova): TRACE: File "/usr/lib/python2.6/site-packages/nova/service.py", line 107, in wait
> (nova): TRACE: service.wait()
> (nova): TRACE: File "/usr/lib/python2.6/site-packages/eventlet/greenthread.py", line 166, in wait
> (nova): TRACE: return self._exit_event.wait()
> (nova): TRACE: File "/usr/lib/python2.6/site-packages/eventlet/event.py", line 116, in wait
> (nova): TRACE: return hubs.get_hub().switch()
> (nova): TRACE: File "/usr/lib/python2.6/site-packages/eventlet/hubs/hub.py", line 177, in switch
> (nova): TRACE: return self.greenlet.switch()
> (nova): TRACE: File "/usr/lib/python2.6/site-packages/eventlet/greenthread.py", line 192, in main
> (nova): TRACE: result = function(*args, **kwargs)
> (nova): TRACE: File "/usr/lib/python2.6/site-packages/nova/service.py", line 77, in run_server
> (nova): TRACE: server.start()
> (nova): TRACE: File "/usr/lib/python2.6/site-packages/nova/service.py", line 137, in start
> (nova): TRACE: self.manager.init_host()
> (nova): TRACE: File "/usr/lib/python2.6/site-packages/nova/volume/manager.py", line 81, in init_host
> (nova): TRACE: self.driver.check_for_setup_error()
> (nova): TRACE: File "/usr/lib/python2.6/site-packages/nova/volume/driver.py", line 92, in check_for_setup_error
> (nova): TRACE: % FLAGS.volume_group)
> (nova): TRACE: Error: volume group nova-volumes doesn't exist
> (nova): TRACE:
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

Revision history for this message
Rob Neff (robpneff) said :
#2

I wish this had been in the documentation for installing OpenStack on RHEL.

Revision history for this message
Damonwinner (d-zamosenchuk) said :
#3

I have similar problem. i make nova-volumes group. But after reboot this group disappeared.
I describe problem here: http://forums.openstack.org/viewtopic.php?f=16&t=611
try to make:
1. i made backup:
vgcfgbackup -f /usr/local/nova-volume
2. and after reboot make restore:
losetup -f --show /var/lib/nova/nova-volumes.img > /dev/loop0
vgcfgrestore -f /usr/local/nova-volume nova-volumes
But it don't helps. I see, when i create EBS volume, in foder /dev created dm-0, dm-1.... devices. And created /dev/nova-volumes with symbolic links to volumes. And in folder /dev/mapper created symbolic links for volumes too. But after reboot this items disappeared. If i make euca-describe-volumes, i see all volumes. But i can't attach and delete.