yahoo-eng-team team mailing list archive

[Mike Perez <thingee@xxxxxxxxx>]

Santiago, that was exactly my point earlier. Those are the only places
that this happens and I don't think it's as simple as you've discussed
to recover. I do agree with Cory in the review that this issue needs to
be addressed, but I think for cases where the other operations to the
backend that would take place while the extend is in progress would
result in false positives of recovering.

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

-- 
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:
  Opinion
Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  If the driver can't extend the volume because 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.

  Expected behavior would be: if the back-end doesn't have enough
  capacity to extend the volume, warn user with proper information and
  set volume status back to 'available' since the volume is untouched.

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