yahoo-eng-team team mailing list archive

[Santiago Baldassin <santiago.b.baldassin@xxxxxxxxx>]

The volume manager does know what happened during the extension and
there's another possible (and likely) failure: not enough space

2014-03-21 07:33:50.009 ERROR cinder.brick.local_dev.lvm [req-7da4bbc0-7b2a-497f-962b-38f15215b383 b6548f770b23478baf8
cecea6c32ea92 a2470742fc4d41ce83c677bc69a6f73c] Error extending Volume
2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm Traceback (most recent call last):
2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm   File "/opt/stack/cinder/cinder/brick/local_dev/lvm.py", lin
e 639, in extend_volume
2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm     run_as_root=True)
2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm   File "/opt/stack/cinder/cinder/utils.py", line 136, in exec
ute
2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm     return processutils.execute(*cmd, **kwargs)
2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm   File "/opt/stack/cinder/cinder/openstack/common/processutil
s.py", line 173, in execute
2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm     cmd=' '.join(cmd))
2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm ProcessExecutionError: Unexpected error while running command
.
2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm Command: sudo cinder-rootwrap /etc/cinder/rootwrap.conf lvext
end -L 12g stack-volumes/volume-a3a21fc8-4bc1-4451-bbb3-808cc363aca1
2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm Exit code: 5
2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm Stdout: '  Extending logical volume volume-a3a21fc8-4bc1-4451
-bbb3-808cc363aca1 to 12.00 GiB\n'
2014-03-21 07:33:50.009 TRACE cinder.brick.local_dev.lvm Stderr: '  Insufficient free space: 2816 extents needed, but 
only 2306 available\n'

I'm ok with generating an explicit exception for "no space left" and as
I stated in my previous comment, we could just show that exception to
the users.

Once again, if a user wants to extend a volume and he is not able to do
it because there's not enough space, that volume should remain
usable/available. It's just wrong to set the volume status to
"error_extending" because there was not enough space to extend the
volume

** Changed in: cinder
       Status: Invalid => New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1294132

Title:
  Volume status set to "error extending" when driver fails to extend the
  volume

Status in Cinder:
  New
Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  If the driver can't extend the volume because for example, there's no
  enough space, the volume status is set to "error_extending" and the
  volume becomes unusable. The only options to the users are to delete
  the volume and create it again

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1294132/+subscriptions