Bug 2061798

Summary:	[ACM 2.5] The service of Cluster Proxy addon was missing
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	Song Lai <slai>
Component:	Cluster Lifecycle	Assignee:	Jian Qiu <jqiu>
Status:	CLOSED ERRATA	QA Contact:	Hui Chen <huichen>
Severity:	high	Docs Contact:	Christopher Dawson <cdawson>
Priority:	high
Version:	rhacm-2.5	CC:	dhuynh, yliu1, yuhe
Target Milestone:	---	Keywords:	Reopened
Target Release:	rhacm-2.5	Flags:	bot-tracker-sync: rhacm-2.5+
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:	2022-06-09 02:09:07 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:

Description Song Lai 2022-03-08 15:07:10 UTC

Description of the problem:
Cannot access spoke via cluster proxy due to the service of Cluster Proxy addon was missing.

Release version:
2.5

Operator snapshot version:
2.5.0-DOWNSTREAM-2022-03-03-12-02-15

OCP version:
4.9.11

Browser Info:
Firefox

Steps to reproduce:
1. Enable cluster proxy addon.
2. Configure valid access token for managed cluster on spoke side.
3. Configure the cluster-proxy kubeconfig on Hub.
4. Get spoke resource from hub.

Actual results:
Can not get spoke resource from hub.

Expected results:
Can get spoke resource from hub.

Additional info:

Comment 1 Song Lai 2022-03-16 03:22:23 UTC

Verified with build 2.5.0-DOWNSTREAM-2022-03-14-18-18-07.

Comment 4 errata-xmlrpc 2022-06-09 02:09:07 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 2.5 security updates, images, and bug fixes), 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-2022:4956