Cinder

  1. Bug #1183283
  2. Comment #1

Comment 1 for bug 1183283

Revision history for this message
Kashyap Chamarthy (kashyapc) wrote : Re: On a fresh devstack install, creating a new cinder volume fails with "Logical volume" exists.

More contextual information from the SCREEN log:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[...]
2013-05-23 04:55:39.218 TRACE cinder.volume.driver Traceback (most recent call last):
2013-05-23 04:55:39.218 TRACE cinder.volume.driver File "/opt/stack/cinder/cinder/volume/driver.py", line 88, in _try_execute
2013-05-23 04:55:39.218 TRACE cinder.volume.driver self._execute(*command, **kwargs)
2013-05-23 04:55:39.218 TRACE cinder.volume.driver File "/opt/stack/cinder/cinder/utils.py", line 193, in execute
2013-05-23 04:55:39.218 TRACE cinder.volume.driver cmd=' '.join(cmd))
2013-05-23 04:55:39.218 TRACE cinder.volume.driver ProcessExecutionError: Unexpected error while running command.
2013-05-23 04:55:39.218 TRACE cinder.volume.driver Command: sudo cinder-rootwrap /etc/cinder/rootwrap.conf lvcreate -L 1G -n volume-b1f03e26-2a80-4a9d-9c2b-428d62e3fe29 stack-volumes
2013-05-23 04:55:39.218 TRACE cinder.volume.driver Exit code: 5
2013-05-23 04:55:39.218 TRACE cinder.volume.driver Stdout: ''
2013-05-23 04:55:39.218 TRACE cinder.volume.driver Stderr: ' Logical volume "volume-b1f03e26-2a80-4a9d-9c2b-428d62e3fe29" already exists in volume group "stack-volumes"\n'
2013-05-23 04:55:39.218 TRACE cinder.volume.driver
2013-05-23 04:55:40.220 DEBUG cinder.utils [req-6367045a-60d7-43de-b011-442de86000ae f55e931102fa473083b5ac048b805a97 988c13aa9fb64d45a8999ccd4425be1f] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf lvcreate -L 1G -n volume-b1f03e26-2a80-4a9d-9c2b-428d62e3fe29 stack-volumes from (pid=12748) execute /opt/stack/cinder/cinder/utils.py:169
2013-05-23 04:55:40.410 DEBUG cinder.utils [req-6367045a-60d7-43de-b011-442de86000ae f55e931102fa473083b5ac048b805a97 988c13aa9fb64d45a8999ccd4425be1f] Result was 5 from (pid=12748) execute /opt/stack/cinder/cinder/utils.py:186
2013-05-23 04:55:40.411 ERROR cinder.volume.driver [req-6367045a-60d7-43de-b011-442de86000ae f55e931102fa473083b5ac048b805a97 988c13aa9fb64d45a8999ccd4425be1f] Recovering from a failed execute. Try number 2
2013-05-23 04:55:40.411 TRACE cinder.volume.driver Traceback (most recent call last):
2013-05-23 04:55:40.411 TRACE cinder.volume.driver File "/opt/stack/cinder/cinder/volume/driver.py", line 88, in _try_execute
2013-05-23 04:55:40.411 TRACE cinder.volume.driver self._execute(*command, **kwargs)
2013-05-23 04:55:40.411 TRACE cinder.volume.driver File "/opt/stack/cinder/cinder/utils.py", line 193, in execute
2013-05-23 04:55:40.411 TRACE cinder.volume.driver cmd=' '.join(cmd))
2013-05-23 04:55:40.411 TRACE cinder.volume.driver ProcessExecutionError: Unexpected error while running command.
2013-05-23 04:55:40.411 TRACE cinder.volume.driver Command: sudo cinder-rootwrap /etc/cinder/rootwrap.conf lvcreate -L 1G -n volume-b1f03e26-2a80-4a9d-9c2b-428d62e3fe29 stack-volumes
2013-05-23 04:55:40.411 TRACE cinder.volume.driver Exit code: 5
2013-05-23 04:55:40.411 TRACE cinder.volume.driver Stdout: ''
2013-05-23 04:55:40.411 TRACE cinder.volume.driver Stderr: ' Logical volume "volume-b1f03e26-2a80-4a9d-9c2b-428d62e3fe29" already exists in volume group "stack-volumes"\n'
2013-05-23 04:55:40.411 TRACE cinder.volume.driver
[...]