If evacuation fails, periodic server state poll can loop forever
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
masakari |
Fix Released
|
Undecided
|
Mark Goddard | ||
Train |
Fix Released
|
Undecided
|
Unassigned | ||
Ussuri |
Fix Released
|
Undecided
|
Unassigned | ||
Victoria |
Fix Released
|
Undecided
|
Unassigned | ||
Wallaby |
Fix Released
|
Undecided
|
Mark Goddard |
Bug Description
Steps to reproduce
==================
Trigger a host failure of a node with instances running on it.
Cause evacuation to fail for some reason. In my case this was caused by using volume encryption, which fails with evacuation since the user used by masakari to trigger evacuation does not have read access to the volume's encryption key in barbican [1].
Expected results
================
Masakari detects the evacuation failure and aborts the failover.
Actual results
==============
The periodic looping call to wait for evacuation (_wait_
Call get server command for instance <UUID>
Environment
===========
Kolla Ansible
Train
CentOS 8
description: | updated |
Changed in masakari: | |
status: | In Progress → Fix Committed |
Possibly this bug relates to the failure to detect evacuation failover: https:/ /bugs.launchpad .net/masakari/ +bug/1859406. Here we will cover the lack of looping call termination.