Bug 2116329 - cluster-proxy-agent not startup due to the imagepullbackoff on spoke cluster
Summary: cluster-proxy-agent not startup due to the imagepullbackoff on spoke cluster
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Cluster Lifecycle
Version: rhacm-2.6
Hardware: All
OS: All
urgent
urgent
Target Milestone: ---
: rhacm-2.6
Assignee: Le Yang
QA Contact: Hui Chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-08 09:57 UTC by Hui Chen
Modified: 2022-09-06 22:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-06 22:35:31 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.6+
cbynum: rhacm-2.6.z+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 24954 0 None None None 2022-08-08 11:52:59 UTC
Red Hat Product Errata RHSA-2022:6370 0 None None None 2022-09-06 22:35:39 UTC

Comment 2 bot-tracker-sync 2022-08-15 16:21:41 UTC 
G2Bsync 1208145115 comment 
 xuezhaojun Mon, 08 Aug 2022 13:39:23 UTC 
 G2Bsync Hello @hchenxa  Is cluster-proxy-prox-agent stay in ns `open-cluster-management-agent-addon` this FC3 release?
Comment 3 bot-tracker-sync 2022-08-15 16:21:43 UTC 
G2Bsync 1208153266 comment 
 xuezhaojun Mon, 08 Aug 2022 13:46:18 UTC 
 G2Bsync Can you also run `kubectl get managedproxyconfiguration -oyaml` and append the result in this issue?
Comment 4 bot-tracker-sync 2022-08-15 16:21:44 UTC 
G2Bsync 1208169666 comment 
 xuezhaojun Mon, 08 Aug 2022 14:00:24 UTC 
 G2Bsync The fix time is very close to the image release time, I have a feeling that fix is not in...
Comment 5 bot-tracker-sync 2022-08-15 16:21:45 UTC 
G2Bsync 1209333534 comment 
 xuezhaojun Tue, 09 Aug 2022 12:43:25 UTC 
 G2Bsync  The fix is include in the lastest code.
Comment 9 errata-xmlrpc 2022-09-06 22:35:31 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 (Moderate: Red Hat Advanced Cluster Management 2.6.0 security updates 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:6370
Note You need to log in before you can comment on or make changes to this bug.