_destroy_evacuated_instances fails randomly with high number of instances
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Robert Tingirica | ||
Icehouse |
Fix Released
|
High
|
Adelina Tuvenie |
Bug Description
In our production environment (2013.2.1), we're facing a random error thrown while starting nova-compute in Hyper-V nodes.
The following exception is thrown while calling '_destroy_
16:30:58.802 7248 ERROR nova.openstack.
2014-03-05 16:30:58.802 7248 TRACE nova.openstack.
(...)
2014-03-05 16:30:58.802 7248 TRACE nova.openstack.
2014-03-05 16:30:58.802 7248 TRACE nova.openstack.
2014-03-05 16:30:58.802 7248 TRACE nova.openstack.
Full trace: http://
Our first guess is that this problem is related with number of instances in our deployment (~3000), they're all fetched in order to check evacuated instances (as Hyper-V is not implementing "list_instance_
In the case of KVM, this error is not happening as it's using a smarter method to get this list based on the UUID of the instances.
Although this is being reported using Hyper-V, it's a problem that could occur in other drivers not implementing "list_instance_
Changed in nova: | |
assignee: | nobody → Alessandro Pilotti (alexpilotti) |
importance: | Undecided → High |
description: | updated |
summary: |
- _destroy_evacuated_instances fails randomly with high number of deleted + _destroy_evacuated_instances fails randomly with high number of instances |
tags: | added: icehouse-rc-potential |
tags: |
added: icehouse-backport-potential removed: icehouse-rc-potential |
Changed in nova: | |
milestone: | none → juno-1 |
Changed in nova: | |
assignee: | Alessandro Pilotti (alexpilotti) → Robert Tingirica (rtingirica) |
Changed in nova: | |
milestone: | none → juno-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-3 → 2014.2 |
Fix proposed to branch: master /review. openstack. org/79961
Review: https:/