Scheduler should handle instance being deleted

Bug #1191126 reported by Phil Day on 2013-06-14
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Medium
Phil Day

Bug Description

Currently if an instance is deleted whilst the scheduler is looking for a suitable host it will log an error due to the InstanceNotFound exception being raised when it goes to update the scheduled_at value.

This isn't really an error as a user can delete an instance at any time, and some tests frameworks seem to do this very quickly.

Phil Day (philip-day) on 2013-06-14
Changed in nova:
assignee: nobody → Phil Day (philip-day)
status: New → In Progress
Sean Dague (sdague) on 2013-07-19
Changed in nova:
importance: Undecided → Medium

Reviewed: https://review.openstack.org/33122
Committed: http://github.com/openstack/nova/commit/79039a7f6ffce2d5cc2e92eee03de94a3c2292f8
Submitter: Jenkins
Branch: master

commit 79039a7f6ffce2d5cc2e92eee03de94a3c2292f8
Author: Phil Day <email address hidden>
Date: Fri Jun 14 22:21:22 2013 +0100

    Handle instance being deleted while in filter scheduler

    Adds handling of InstanceNotFound when trying to update the
    scheduled_at time of an instance.

    Users can delete an instance at any time (and many test
    cases delete very quickly), so this should be a warning
    not an error

    Fixes bug 1191126

    Change-Id: I72b296668f60b1de71ff8c6d7bbb749023d89f12

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2013-09-05
Changed in nova:
milestone: none → havana-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-10-17
Changed in nova:
milestone: havana-3 → 2013.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers