yahoo-eng-team team mailing list archive

[Dan Smith <dms@xxxxxxxxxxxxx>]

This *is* by design because the call to start the resize is cast-ed
(like almost everything else) from the api node and returns immediately.
We don't know that it failed until potentially much later. I'm going to
mark this as invalid, but if I'm missing something, please reopen.

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

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

Title:
  Resize doesn't fail when the operation doesn't complete

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  I've noticed nova resize doesn't fail on the client side when the
  server doesn't actually do the resize. 2 examples:

   * resizing to a flavor with too much RAM. The scheduler can't find a
  host, but the command line call succeeds, and the server state stays
  the same.

   * resizing a shutdown server, where nothing seems to be happening.

  Using devstack and latest master.

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