Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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
(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.
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