System unresponsive after Active node reboot.

Bug #1887501 reported by Akshay on 2020-07-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Brief Description
Setup: I have StarlingX duplex mode setup up and running. I am able to spawn VMs on it.

Test Case: Testing instance HA.

Issue: After active node reboot, I am not able to take ssh on standby node. The console stucks on standby node and I don't see the the hostname where we enter commands. The overall system went down. The rebooted node comes up but not able to see anything on it as it is showing keystone unavailable. No StarlingX GUI and openstack services are available at this time.

Steps already taken : Rebooted both the nodes again to bring the setup in stable state again.

Can you please help me to find the reason of this.


Steps to Reproduce
1. Deploy Bare Metal StarlingX R2 duplex mode.
2. Spawn VM.
3. Reboot Active node.

Expected Behavior
VM should be rebuilt on standby node smoothly.

Actual Behavior
Setup went in unresponsive state.

Its Random. Comes occasionally.

System Configuration
Two node system

Last Pass

Ghada Khalil (gkhalil) on 2020-07-18
tags: added: stx.2.0
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers