Bug 1973635

Summary:	Post Live-migration tasks fail and leave nova.instances table with incorrect host/node values
Product:	Red Hat OpenStack	Reporter:	kforde
Component:	openstack-nova	Assignee:	OSP DFG:Compute <osp-dfg-compute>
Status:	CLOSED DUPLICATE	QA Contact:	OSP DFG:Compute <osp-dfg-compute>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16.1 (Train)	CC:	dasmith, eglynn, jhakimra, kchamart, mporrato, sbauza, sgordon, smooney, vromanso
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-18 12:26:38 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:

Comment 1 smooney 2021-06-18 12:26:38 UTC

closing this as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1955031
this is not really a nova bug but a misconfiguration of the neutorn timeouts too compenstate for the excessive slowness of the neutron api responces.

the workaround is to increase the neutron client timeouts both on nova and neutron wsgi server but also in haproxy to allow nova to wiat for the eventual response form neutron.

*** This bug has been marked as a duplicate of bug 1955031 ***