Bug 2176828

Summary:	redis bundle resource stopped on one controller in pcs status and unable to spawn vm
Product:	Red Hat OpenStack	Reporter:	visinha
Component:	redis	Assignee:	OSP Team <rhos-maint>
Status:	CLOSED CANTFIX	QA Contact:	Leonid Natapov <lnatapov>
Severity:	medium	Docs Contact:
Priority:	low
Version:	16.2 (Train)	CC:	apevec, jmarcian, lhh, lmiccini, lnatapov, mrunge, nathans, parthee
Target Milestone:	---	Keywords:	Triaged, ZStream
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:	2023-08-10 11:10:34 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 Leonid Natapov 2023-03-15 14:38:55 UTC

We don't quite understand what is the connection between the Redis and not being able to launch VMs. It seems like ovn-dbs bundle is the reason for that.
If customer could reproduce the issue and restart only ovn-dbs bundle and see if that's solves the problem.
Also we would like to see redis logs before and after redis stopped running.

Comment 3 Matthias Runge 2023-03-20 08:22:28 UTC

From the report it is not clear if redis and ovn-db were restarted in the same step? Redis is not used when instances are launched.
A network disruption could explain the issues described and seen here.

CloudOps does not maintain redis or pacemaker.