Bug 1989287

Summary:	pmproxy not working if redis is still loading data during startup
Product:	Red Hat Enterprise Linux 8	Reporter:	Amey <abetkike>
Component:	pcp	Assignee:	Andreas Gerstmayr <agerstmayr>
Status:	CLOSED ERRATA	QA Contact:	Jan Kurik <jkurik>
Severity:	unspecified	Docs Contact:	Jacob Taylor Valdez <jvaldez>
Priority:	unspecified
Version:	8.4	CC:	agerstmayr, jkurik, nathans, peter.vreman
Target Milestone:	beta	Keywords:	Bugfix, Triaged
Target Release:	8.6	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pcp-5.3.5-1.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-10 13:30:52 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 Mark Goodwin 2021-08-03 00:27:10 UTC

This bug needs essentially the same fix as upstream issue #1357:
#1357 pmproxy redis connect/reconnect 
https://github.com/performancecopilot/pcp/issues/1357


If pmproxy redis config is enabled but the initial version check fails to connect, then pmproxy should periodically retry until successful. It's the same fix whether redis isn't enabled/started or if it's too busy starting-up/loading. Either way, pmproxy should retry rather than have to be restarted.

Comment 2 Peter Vreman 2021-08-04 15:47:18 UTC

Mark,

Confirming from my user perspective that the retry is the best solution that will solve more than this single version check failure.

Does the planned fix for adding retry also include the scenario that redis is restarted during the lifetime of pmproxy?

Peter

Comment 3 Nathan Scott 2021-08-04 22:22:53 UTC

(In reply to Peter Vreman from comment #2)
> Mark,
> 

(I'll answer for Mark today as he's on PTO)

> Confirming from my user perspective that the retry is the best solution that
> will solve more than this single version check failure.

Thanks.

> Does the planned fix for adding retry also include the scenario that redis
> is restarted during the lifetime of pmproxy?

Yes.

Comment 10 errata-xmlrpc 2022-05-10 13:30:52 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (pcp bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:1765