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.
Bug 1989287 - pmproxy not working if redis is still loading data during startup
Summary: pmproxy not working if redis is still loading data during startup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcp
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: 8.6
Assignee: Andreas Gerstmayr
QA Contact: Jan Kurik
Jacob Taylor Valdez
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-02 20:33 UTC by Amey
Modified: 2022-05-10 13:49 UTC (History)
4 users (show)

Fixed In Version: pcp-5.3.5-1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-10 13:30:52 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-91979 0 None None None 2021-08-02 20:35:09 UTC
Red Hat Product Errata RHBA-2022:1765 0 None None None 2022-05-10 13:31:02 UTC

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
Note You need to log in before you can comment on or make changes to this bug.