Incorrect flavor ref is returned briefly after a resize is reverted

Bug #924371 reported by Daryl Walleck on 2012-01-31
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Brian Waldon

Bug Description

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 can reproduce this issue.

Brian Waldon (bcwaldon) on 2012-02-02
Changed in nova:
status: New → Confirmed
importance: Undecided → Low
milestone: none → essex-4
Brian Waldon (bcwaldon) on 2012-02-02
Changed in nova:
assignee: nobody → Brian Waldon (bcwaldon)
status: Confirmed → In Progress
Brian Waldon (bcwaldon) wrote :

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

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

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2012-02-29
Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-4 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers