yahoo-eng-team team mailing list archive

[John Griffith <1294132@xxxxxxxxxxxxxxxxxx>]

So I ran some tests on this, as long as the backend doesn't fail to do
the extend the quota is checked up front and the API responds with an
error before ever changing state or attempting the resize.

This is what I would expect.  If the cmd passes quota check and is sent
to the driver, but the driver fails (ie not enough space) then it raises
the error I think you're seeing and sets the status to error.  This is
what I would expect and I think is appropriate behavior.  It's in line
with how all of the other async calls work.

** Changed in: cinder
       Status: In Progress => 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 new size exceeds quota

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

Bug description:
  extend_volume in cinder.volume.manager should not set the status to
  error_extending when the quota was exceeded. The status should still
  be available

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