nova should not reschedule an instance that has already been deleted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Low
|
Unassigned |
Bug Description
I'm investigating an issue where an instance with a large disk and an attached cinder volume was booted in a stable/kilo OpenStack setup with the diskFilter disabled.
The timeline looks like this:
scheduler picks initial compute node
nova attempts to boot it up on one compute node, it runs out of disk space and gets rescheduled
scheduler picks another compute node
user requests instance deletion
user requests cinder volume deletion
nova attempts to boot it up on second compute node, it runs out of disk space and gets rescheduled
scheduler picks a third compute node
nova attempts to boot it up on third compute node, runs into problems due to missing cinder volume
The issue I want to address in this bug is whether it makes sense to reschedule the instance when the instance has already been deleted.
Also, instance deletion sets the task_state to 'deleting' early on. In compute.
So...would it make sense to have nova-compute put an "expected_
Changed in nova: | |
assignee: | Hans Lindgren (hanlind) → Stephen Finucane (stephenfinucane) |
Changed in nova: | |
status: | In Progress → New |
assignee: | Stephen Finucane (stephenfinucane) → nobody |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |
Fix proposed to branch: master /review. openstack. org/276783
Review: https:/