After failed evacuation the recovered source compute tries to delete the instance
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Oleksiy Molchanov | ||
OpenStack Compute (nova) |
Fix Released
|
High
|
Elod Illes | ||
Ocata |
Fix Committed
|
High
|
Balazs Gibizer | ||
Pike |
Fix Committed
|
High
|
Matt Riedemann | ||
OpenStack Security Advisory |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Description
===========
In case of a failed evacuation attempt the status of the migration is 'accepted' instead of 'failed' so when source compute is recovered the compute manager tries to delete the instance from the source host. However a secondary fault prevents deleting the allocation in placement so the actual deletion of the instance fails as well.
Steps to reproduce
==================
The following functional test reproduces the bug: https:/
What it does: initiate evacuation when no valid host is available and evacuation fails, but nova manager still tries to delete the instance.
Logs:
2017-08-29 19:11:15,751 ERROR [oslo_messaging
NoValidHost: No valid host was found. There are not enough hosts available.
2017-08-29 19:11:16,103 INFO [nova.tests.
2017-08-29 19:11:16,115 INFO [nova.api.
2017-08-29 19:11:16,120 INFO [nova.api.
2017-08-29 19:11:16,131 INFO [nova.api.
2017-08-29 19:11:16,138 INFO [nova.compute.
2017-08-29 19:11:16,146 INFO [nova.api.
2017-08-29 19:11:16,151 INFO [nova.api.
2017-08-29 19:11:16,152 INFO [nova.tests.
2017-08-29 19:11:16,163 INFO [nova.api.
2017-08-29 19:11:16,168 INFO [nova.api.
2017-08-29 19:11:16,176 INFO [nova.api.
2017-08-29 19:11:16,184 INFO [nova.compute.
2017-08-29 19:11:16,192 INFO [nova.api.
2017-08-29 19:11:16,197 INFO [nova.api.
2017-08-29 19:11:16,198 INFO [nova.tests.
2017-08-29 19:11:16,255 INFO [nova.api.
2017-08-29 19:11:16,262 INFO [nova.api.
2017-08-29 19:11:16,280 INFO [nova.api.
2017-08-29 19:11:16,281 INFO [nova.service] Starting compute node (version 16.0.0)
2017-08-29 19:11:16,296 INFO [nova.compute.
description: | updated |
tags: | added: evacuate placement |
summary: |
- Failed evacuation also tries to delete the VM + After failed evacuation the recovered source compute tries to delete the + instance |
Changed in nova: | |
assignee: | nobody → Illes Elod (elod-illes) |
status: | Triaged → In Progress |
Changed in nova: | |
assignee: | Illes Elod (elod-illes) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Illes Elod (elod-illes) |
no longer affects: | nova/newton |
Changed in fuel: | |
assignee: | nobody → Oleksiy Molchanov (omolchanov) |
importance: | Undecided → High |
status: | New → Confirmed |
milestone: | none → 9.2-mu-11 |
Changed in fuel: | |
status: | Confirmed → Fix Committed |
A regression test was pushed for this bug https:/ /review. openstack. org/#/c/ 498482/. (It seems that the automatic linking doesn't work in later patch sets)