rejoin-stack.sh fails setup nova-volume

Bug #1032269 reported by Tong Li
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
devstack
Won't Fix
Medium
Unassigned

Bug Description

After setup openstack by running stack.sh, everything works fine. After restart your machine, then run rejoin-stack.sh from devstack directory, you will see that the nova-volume is not set up correctly.

2012-08-02 12:02:04 DEBUG cinder.utils [req-19972905-919f-4560-b088-ac02849355b6 None None] Running cmd (subprocess): sudo /usr/local/bin/cinder-rootwrap /etc/cinder/rootwrap.conf vgs --noheadings -o name from (pid=2835) execute /opt/stack/cinder/cinder/utils.py:193
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 336, in fire_timers
    timer()
  File "/usr/lib/python2.7/dist-packages/eventlet/hubs/timer.py", line 56, in __call__
    cb(*args, **kw)
  File "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 192, in main
    result = function(*args, **kwargs)
  File "/opt/stack/cinder/cinder/service.py", line 88, in run_server
    server.start()
  File "/opt/stack/cinder/cinder/service.py", line 159, in start
    self.manager.init_host()
  File "/opt/stack/cinder/cinder/volume/manager.py", line 96, in init_host
    self.driver.check_for_setup_error()
  File "/opt/stack/cinder/cinder/volume/driver.py", line 107, in check_for_setup_error
    % FLAGS.volume_group)
Error: volume group stack-volumes doesn't exist

Revision history for this message
Dean Troyer (dtroyer) wrote :

This also appears to occur with Cinder

Changed in devstack:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Dean Troyer (dtroyer) wrote :

The issue is that the loopback creation for the stack-volumes volume group is not performed by rejoin-stack.sh. It only happens after a reboot, not after unstack.sh.

Changed in devstack:
status: Confirmed → Triaged
Dean Troyer (dtroyer)
Changed in devstack:
status: Triaged → Won't Fix
Revision history for this message
Ben Davis (bendavis78) wrote :

Just curious -- why was this closed as wontfix?

If anyone else is experiencing this issue, you can try running the following before running rejoin-stack.sh:

sudo losetup -f /opt/stack/data/stack-volumes-backing-file

Revision history for this message
Genc Tato (gtato6) wrote :

Tried
sudo losetup -f /opt/stack/data/stack-volumes-backing-file

but still the same error. I am not sure what won't fix means in this case, but sounds weird.

Revision history for this message
melanie witt (melwitt) wrote :

@Ben That worked for me, thank you for sharing!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.