** Changed in: horizon
Status: In Progress => Invalid
** 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/129413
So the implementation to fix this was not okI'm cool with that and
I'll try to find a better way to fix this issue. In the meantime I'll
add a description in Horizon warning the user that if there's not enough
space the extend operation will fail and the volume will become
unusable.
** Changed
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 wo
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
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
5 matches
Mail list logo
