yahoo-eng-team team mailing list archive

[Huang Zhiteng <winston.d@xxxxxxxxx>]

As the volume manager doesn't know what exactly happened during the
extending, and there are actually two kinds of possible failure (a.
volume was untouched; b. very very unlikely volume was touched or even
corrupted), it's safer to set volume state to 'error_extending' instead
of reset it back to 'available'.

Unless Cinder is actually able to confirm volume is in sane state, we
have to keep current behavior.

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

-- 
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:
  Invalid
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