Bug 1942589

Summary: cluster became offline after apiserver health check
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Gellert Kis <gekis>
Component: Cluster LifecycleAssignee: James Talton <jtalton>
Status: CLOSED ERRATA QA Contact: Derek Ho <dho>
Severity: high Docs Contact: Christopher Dawson <cdawson>
Priority: high    
Version: rhacm-2.2CC: dhuynh, juhsu
Target Milestone: ---Flags: dhuynh: qe_test_coverage+
juhsu: rhacm-2.2.z+
ming: rhacm-2.3+
Target Release: rhacm-2.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-06 00:51:36 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 5 juhsu 2021-08-05 20:29:28 UTC
Fixed in 2.2.5 and 2.3.

Comment 6 errata-xmlrpc 2021-08-06 00:51:36 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 (Important: Red Hat Advanced Cluster Management for Kubernetes version 2.3), 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/RHSA-2021:3016