Bug 2232619

Summary:	[OSP16.2] Unable to instantiate VM, stuck in spawning status
Product:	Red Hat OpenStack	Reporter:	Matsvei Hauryliuk <mhauryli>
Component:	openstack-nova	Assignee:	OSP DFG:Compute <osp-dfg-compute>
Status:	CLOSED NOTABUG	QA Contact:	OSP DFG:Compute <osp-dfg-compute>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16.2 (Train)	CC:	alifshit, dasmith, eglynn, jhakimra, kchamart, sbauza, sgordon, vromanso
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-21 16:17:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matsvei Hauryliuk 2023-08-17 14:49:52 UTC

Description of problem:

VMs are in spawning status until they time out.
All DPDK nodes were redeployed and neutron & ovn-controller services were restarted but the issue still persists.

The env:
OSP 16.2, RHEL 8.4, 3 DPDK computes

The cluster has 3 kind of computes:
11 generic 
3 OVS DPDK 
13 Compute SRIOV

But only the DPDK ones experience this issue.

Version-Release number of selected component (if applicable):

How reproducible:
Happens each time

Steps to Reproduce:
1.$ openstack --debug --timings server create --image rhel-8.4 --flavor medium.dpdk --network test-dpdk-net3 test-dpdk-vm9

Actual results:
Timeout when launching VM.

Expected results:
VM spawning correctly.

Additional info:
Another cluster deployed with the same set of templates does not experience these issues.
Attached to the bug are Sosreports from the compute node experiencing the issue as well as from a controller node,
also the outputs of

openstack network agent list --fit
openstack compute service list --fit
openstack volume service list --fit