Bug 1942589 - cluster became offline after apiserver health check
Summary: cluster became offline after apiserver health check
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Cluster Lifecycle
Version: rhacm-2.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: rhacm-2.3
Assignee: James Talton
QA Contact: Derek Ho
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-24 15:16 UTC by Gellert Kis
Modified: 2022-02-14 22:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-06 00:51:36 UTC
Target Upstream Version:
Embargoed:
dhuynh: qe_test_coverage+
juhsu: rhacm-2.2.z+
ming: rhacm-2.3+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github open-cluster-management backlog issues 10823 0 None None None 2021-03-25 15:44:03 UTC
Red Hat Product Errata RHSA-2021:3016 0 None None None 2021-08-06 00:52:11 UTC

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