The resize call is asynchronous - eg the API returns the 202 to the
client possibly before the actual resize attempt is made. 202 just means
that the request has been accepted, not that it has been accepted. In
order to determine if the resize has succeded you need to poll
** 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/1234418
Title:
nova resize return 202 and host left in ERROR state
Status in OpenStack Compute (Nova):
Invalid
Bug description:
The nova resize return 202, but leave the host in ERROR state. The new
size is within the quota. Steps to reproduce:
1. create a node with m1.tiny flavor using nova boot.
2. wait for the state to change as ACTIVE
3. resize the node to m1.small flavor.
Obtained result:
The resize is successful. 202 code is returned. The state is set as ERROR.
This cause the following tempest tests fail. The tests attempt to resize the
host beyond the quota and expect OverLimit exception. Since the API return 202
status, the tests fail.
test_resize_server_using_overlimit_ram
test_resize_server_using_overlimit_vcpus
Refer to the debug output for details:
http://pastebin.com/XD3ZbEL5
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1234418/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
