StarlingX R2 duplex: VM stucked in spawning state for 2-days.

[Akshay]

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

Test Case: I simply spawned one VM through horizon.

Issue: It got stuck in spawning state for hours. So just to check the limit, I left that VM as it is and it was in spawning state for 2 days. Then I manually deleted that VM and again spawned the VM with same configuration and it gets spawned as expected.

I have seen this behavior 3 times out of many while testing some other test cases.
Please guide me to find the real issue.

Severity
--------

Critical

Steps to Reproduce
------------------
1. Deploy Bare Metal StarlingX R2 duplex mode.
2. Spawn a VM from horizon.

Expected Behavior
------------------
VM should get spawned gracefully.

Actual Behavior
----------------
VM stucks in spawning state.

Reproducibility
---------------
Reproducible

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

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

[Ghada Khalil (gkhalil)]

Assigning to distro.openstack PL for review

[yong hu (yhu6)]

This issue will be handled in R2 next maintenance release.
To take it with "medium" importance because it was not 100% blocked.

[zhipeng liu (zhipengs)]

Dear Akshay,

Firstly, please check if your hardware resource is enough or limited.
Secondly, please check the logs in /var/log/containers/*.log, especially, nova-compute, nova-schedule, placement.log, to see where it stuck and what it is waiting for.
If you still could not find any clue, please attach your logs here.

Thanks!
Zhipeng

[yong hu (yhu6)]

changed the priority to low since there was no response from @Akshay since 2019 Nov.

[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.