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

[Akshay]

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

[Ghada Khalil (gkhalil)]

This issue was reported for stx.2.0. There are no logs for further investigation. Since then, stx.3.0 has become available and stx.4.0 is soon to be released (July 2020).

Suggest trying one of the newer releases and opening a new LP with more data (collect logs) if the issue persists.

[Ramaswamy Subramanian (rsubrama)]

No progress on this bug for more than 2 years. Candidate for closure.

If there is no update, this issue is targeted to be closed as 'Won't Fix' in 2 weeks.

[Ramaswamy Subramanian (rsubrama)]

Changing the status to 'Won't Fix' as there is no activity.