migration of anti-affinity server fails due to stale scheduler instance info
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Balazs Gibizer | ||
Pike |
Invalid
|
Low
|
Unassigned | ||
Queens |
Invalid
|
Low
|
Balazs Gibizer | ||
Rocky |
Fix Released
|
Low
|
Balazs Gibizer | ||
Stein |
Fix Released
|
Low
|
Elod Illes | ||
Train |
Fix Released
|
Low
|
Elod Illes | ||
Ussuri |
Fix Released
|
Low
|
Balazs Gibizer |
Bug Description
Description
===========
Steps to reproduce
==================
Have a deployment with 3 compute nodes
* make sure that the deployment is configured with tracks_
* create and server group with anti-affinity policy
* boot server1 into the group
* boot server2 into the group
* migrate server2
* confirm the migration
* boot server3
Make sure that between the last two steps there was no periodic _sync_scheduler
Expected result
===============
server3 is booted on the host where server2 is moved away
Actual result
=============
server3 cannot be booted (NoValidHost)
Triage
======
The confirm resize call on the source compute does not update the scheduler that the instance is removed from this host. This makes the scheduler instance info stale and causing the subsequent scheduling error.
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Low |
assignee: | nobody → Balazs Gibizer (balazs-gibizer) |
tags: | added: compute scheduler |
Fix proposed to branch: master /review. opendev. org/714997
Review: https:/