Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2056968

Summary: Fix Proxy support in RHACM 2.4.2
Product: OpenShift Container Platform Reporter: Mario Vázquez <mavazque>
Component: Telco EdgeAssignee: Ian Miller <imiller>
Telco Edge sub component: ZTP QA Contact: yliu1
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: cdawson, mfilanov
Version: 4.9   
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-26 16:43:57 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:
Bug Depends On:    
Bug Blocks: 2057721    

Description Mario Vázquez 2022-02-22 13:13:14 UTC 
Description of problem:

The new assisted service API v2 requires the proxy settings to be added to the InfraEnv and also to the AgentClusterInstall. The current version of the PolicyGenTool only adds the proxy settings to the Infraenv which ends up in a failed installation.

The current RHACM release (2.4.1) is missing the updated AgentClusterInstall CRD + Controller so installs requiring proxy will fail.

The next RHACM release (2.4.2) is planned to have this fixes in place: https://bugzilla.redhat.com/show_bug.cgi?id=2056669

I created a test build of the policygentool and was able to run a ZTP deployment using the new CRD and assisted-service controller versions.

Version-Release number of selected component (if applicable):
Not sure which release we should set, worst case scenario if you define the proxy settings in the AgentClusterInstall without the proper CRD/Controller, those settings are removed by the controller.

How reproducible:

Always

Steps to Reproduce:
1. Try to deploy a cluster using ZTP via PolicyGenTool requiring a proxy 
2.
3.

Actual results:
Proxy is defined in the siteconfig and gets added to the InfraEnv but not to the AgentClusterInstall

Expected results:
Proxy is defined in the siteconfig and gets added to the InfraEnv and to the AgentClusterInstall

Additional info: