instance remains on the same host after host reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Invalid
|
Low
|
Unassigned |
Bug Description
Brief Description
-----------------
After rebooting the host to evacuate instances from it the instances recover to active
state, but they sometimes remain on the same host.
Severity
--------
<Major: System/Feature is usable but degraded>
Steps to Reproduce
------------------
1. Create instance(s) on a host
2. reboot host (sudo reboot -f)
3. Waiting for host to reach state(s): {'availability': ['offline', 'failed']}
3. Wait for instances to reach ERROR or REBUILD state
4. Check instances are in Active state and moved to other host
Expected Behavior
------------------
instances get back to active state and are moved the another host
Actual Behavior
----------------
instances remain on the same host that was rebooted
Reproducibility
---------------
<Intermittent>
System Configuration
-------
<Two node system, Multi-node system>
Branch/Pull Time/Commit
-------
###
### StarlingX
### Built from master
###
OS="centos"
SW_VERSION="20.12"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID=
JOB="STX_
<email address hidden>"
BUILD_NUMBER="310"
BUILD_HOST=
BUILD_DATE=
FLOCK_OS="centos"
FLOCK_JOB=
<email address hidden>"
FLOCK_BUILD_
FLOCK_BUILD_
FLOCK_BUILD_
DISTRO_OS="centos"
DISTRO_
<email address hidden>"
DISTRO_
DISTRO_
DISTRO_
COMPILER_
COMPILER_
<email address hidden>"
COMPILER_
COMPILER_
COMPILER_
Test Activity
-------------
[Sanity]
tags: | added: stx.distro.openstack |
Changed in starlingx: | |
importance: | Undecided → Low |
collect added at https:/ /files. starlingx. kube.cengn. ca/launchpad/ 1903968