Bug 1977998 - Applications not working Unexpected Error Please try again
Summary: Applications not working Unexpected Error Please try again
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Search / Analytics
Version: rhacm-2.2
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
: rhacm-2.2.6
Assignee: Jorge Padilla
QA Contact: Atif
Mikela Dockery
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-30 21:49 UTC by Tuan
Modified: 2024-10-01 18:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-10 18:33:12 UTC
Target Upstream Version:
Embargoed:
ashafi: qe_test_coverage?
ming: rhacm-2.2.z+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github open-cluster-management backlog issues 13920 0 None None None 2021-07-01 19:31:02 UTC
Red Hat Product Errata RHBA-2021:3126 0 None None None 2021-08-10 18:33:22 UTC

Comment 3 Mike Ng 2021-07-05 15:42:52 UTC 
G2Bsync 873098296 comment 
 jlpadilla Fri, 02 Jul 2021 15:55:27 UTC 
 G2Bsync
This problem happens because the search-redisgraph pod was not automatically restarted after the ceertiificate was renewed. This bug was fixed in the 2.2.5 release.

As a workaround you can manually restart the pod named search-redisgraph-0 to force a certificate refresh.

Note that it can take up to 10-15 minutes to rebuild the search index after the pod is restarted. This is because the collectors in the managed clusters will be in a backoff state, which prevents from retrying too often after an error.
Comment 10 errata-xmlrpc 2021-08-10 18:33:12 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 (Red Hat Advanced Cluster Management 2.2.6 bug fix 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-2021:3126
Note You need to log in before you can comment on or make changes to this bug.