Instance remains in 'resizing' state if network node is down during resize
Bug #980685 reported by
Unmesh Gurjar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Unmesh Gurjar |
Bug Description
Scenario: While an instance is running (Active state), stop the network service and then resize the instance.
Expected Behavior: Instance resize should fail and instance vm_state should change to 'error'.
Actual Behavior: Instance resizing fails, however, instance remains in vm_state=resizing, task_state=
Branch: master
The instance remains in this state even after the network service comes up again. The instance (in resizing state) cannot be deleted/rebooted.
There needs to be a periodic task that monitors such instances (being in resizing state for long time) and set their vm_state to error.
Changed in nova: | |
assignee: | nobody → Unmesh Gurjar (unmesh-gurjar) |
tags: | added: essex-backport |
Changed in nova: | |
milestone: | none → folsom-1 |
importance: | Undecided → Low |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | folsom-1 → 2012.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/6632
Review: https:/