OpenStack Compute (nova)

Failed build needs to cleanup task state

Bug #1049897 reported by Brian Elliott on 2012-09-12

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Compute (nova)	Fix Released	Undecided	Brian Elliott	OpenStack Compute (nova) 2012.2 "folsom"

Bug Description

A failed build may leave the task state as SPAWNING. If the build gets re-scheduled, this will cause an UnexpectedTaskState error because it is no longer in the SCHEDULING state.

Brian Elliott (belliott) on 2012-09-12

Changed in nova:
assignee:	nobody → Brian Elliott (belliott)

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2012-09-12: Fix proposed to nova (master)

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

Changed in nova:
status:	New → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2012-09-12: Fix merged to nova (master)

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

commit f5ad3bced3788fea89a4a25a29053d51aeb7a3b2
Author: Brian Elliott <email address hidden>
Date: Wed Sep 12 00:49:07 2012 +0000

Reset task state before rescheduling

    Reset the task state to SCHEDULING before attempting re-scheduling.
    This is a precaution to make sure subsequent calls to update the
    task state see an 'expected_task_state'.

bug 1049897

Change-Id: I5667a88487bd7039eb2e0aaebef532199d8b31ef