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

Bug #1852729 reported by Akshay on 2019-11-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

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.



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.


System Configuration
Two node system

Last Pass

Ghada Khalil (gkhalil) wrote :

Assigning to distro.openstack PL for review

tags: added: stx.distro.openstack
Changed in starlingx:
assignee: nobody → yong hu (yhu6)
yong hu (yhu6) wrote :

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

Changed in starlingx:
assignee: yong hu (yhu6) → zhipeng liu (zhipengs)
importance: Undecided → Medium
zhipeng liu (zhipengs) on 2019-11-19
Changed in starlingx:
status: New → In Progress
zhipeng liu (zhipengs) wrote :

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.


Changed in starlingx:
status: In Progress → Incomplete
yong hu (yhu6) on 2019-11-27
Changed in starlingx:
assignee: zhipeng liu (zhipengs) → Akshay (yadavakshay58)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers