Incorrect flavor ref is returned briefly after a resize is reverted

[Daryl Walleck]

I've observed that immediately following a revert resize, the API returns the flavor the server was resizing to, not the original flavor. For example, if I resize a server with flavor 1 and I resize to flavor 2, but then decide to revert, after returning to the ACTIVE status, a GET request for that server may return the incorrect flavor for 1-10 seconds afterwards.

One of the Tempest tests (test_resize_server_revert in test_server_actions.py) can reproduce this issue.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/3725

[Brian Waldon (bcwaldon)]

My two patches add a new REVERT_RESIZE state to make it clear to the client what is going on.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/3725
Committed: http://github.com/openstack/nova/commit/f7deddb89ce63c2ccc7a207461188aeb7a41af32
Submitter: Jenkins
Branch: master

commit f7deddb89ce63c2ccc7a207461188aeb7a41af32
Author: Brian Waldon <email address hidden>
Date: Thu Feb 2 16:28:55 2012 -0800

    Fix status transition when reverting resize

    Present the instance being reverted with a 'REVERT_RESIZE' status instead
    of 'ACTIVE' after a revertResize action is triggered. Fixes bug 924371

    Change-Id: I12e98733fd00c0794fb9a4acb0cc6752ca02e855