StarlingX R2 duplex: After reboot of any node, system takes 25-30 minutes to come up again to work properly.

Bug #1852734 reported by Akshay on 2019-11-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Undecided
Unassigned

Bug Description

Brief Description
-----------------
Setup: I have deployed Bare Metal StarlingX R2 duplex mode.

Test Case: Reboot any one node.

Issue: After reboot of any node, the openstack horizon is initially unavailable for near about 5 minutes. After it, it also takes further 10-15 mins to be stable (observed this behavior after running 50-70 HA related test cases).
If VM is spawned just after initial 5 mins of unavailability, it shows inconsistent behavior like it may go in ERROR state, or it may stuck in SPAWNING state which will need a reboot of both controllers to come in proper working state again.

Please guide me to find the real issue.

Severity
--------

Critical

Steps to Reproduce
------------------
1. Deploy Bare Metal StarlingX R2 duplex mode.
2. Reboot any node.

Expected Behavior
------------------
System should work a way sooner.

Actual Behavior
----------------
system takes near about 25-30 mins to be stable.

Reproducibility
---------------
Not exactly reproducible but seen almost every time in 50-70 HA related test cases.

System Configuration
--------------------
Two node system

Last Pass
---------
NO

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers