Bug 2049874 - Missing proxy configuration support in AgentClusterInstall
Summary: Missing proxy configuration support in AgentClusterInstall
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Infrastructure Operator
Version: rhacm-2.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: rhacm-2.4.3
Assignee: Elior Erez
QA Contact: Song Lai
Derek
URL:
Whiteboard:
Depends On: 2049876 2056669
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-02 20:15 UTC by Elior Erez
Modified: 2025-08-08 12:24 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-03 20:20:49 UTC
Target Upstream Version:
Embargoed:
ccrum: qe_test_coverage+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift assisted-service pull 3279 0 None open Bug 2049874: Proxy support in ACI 2022-02-02 20:27:45 UTC
Github stolostron backlog issues 19649 0 None None None 2022-02-02 23:28:56 UTC
Red Hat Issue Tracker MGMTBUGSM-70 0 None None None 2022-02-02 20:29:17 UTC

Description Elior Erez 2022-02-02 20:15:07 UTC 
Description of the problem:
Proxy configuration support in AgentClusterInstall is missing.
Fix already applied on release-ocm-2.5 on https://github.com/openshift/assisted-service/pull/3215.


Release version: 

Operator snapshot version:

OCP version: 

Browser Info:

How reproducible:
100%

Steps to reproduce:
1. Create AgentClusterInstall with proxy configuration

Actual results: No proxy configurations on AgentClusterInstall resource

Expected results:

Additional info:
Comment 1 Jose Gato 2022-03-04 10:33:31 UTC 
If I am not wrong, the issue solved in the current released RHACM 2.4.2, right?
Comment 2 Chad Crum 2022-03-19 14:49:11 UTC 
(In reply to Jose Gato from comment #1)
> If I am not wrong, the issue solved in the current released RHACM 2.4.2,
> right?

Hi Jose- Yes this was fixed in 2.4.2. We actually validated this a few weeks ago and confirmed it was working on 2.4.2.
Note You need to log in before you can comment on or make changes to this bug.