Bug 1984400

Summary:	Capsule upgrade/install fails due to proxy configuration in 'HTTP(S) proxy' in settings
Product:	Red Hat Satellite	Reporter:	rakesh kumar <rakumar>
Component:	Foreman Proxy	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Vladimír Sedmík <vsedmik>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.9.0	CC:	ahumbe, aruzicka, ehelms, gsulliva, inecas, jpathan, lvrtelov, zhunting
Target Milestone:	6.12.0	Keywords:	PrioBumpGSS, Triaged, Upgrades
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	foreman-3.3.0.3-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-16 13:32:43 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 rakesh kumar 2021-07-21 11:21:45 UTC

Description of problem:

If we have a proxy set in Administer -> Settings -> General -> 'HTTP(S) proxy' then capsule installation/upgrade fails because Satellite is not able to connect to capsule through proxy. In this scenario, the solution is to either remove the proxy or add the capsule in 'HTTP(S) proxy except hosts' list. 


Version-Release number of selected component (if applicable):
Satellite 6.x


How reproducible:
Always

Steps to Reproduce:
1. Set the proxy in Administer -> Settings -> General -> 'HTTP(S) proxy'
2. Proxy should not be configured for internal routing
3. Try installing or upgrade the existing capsule.

Actual results:
Installation or upgrade fails. 


Expected results:

We should add the capsule FQDN in 'HTTP(S) proxy except hosts' automatically at the time of certificate generation on the Satellite or in some other way to prevent such issues.


Additional info:

Comment 4 Adam Ruzicka 2022-06-01 11:20:15 UTC

Created redmine issue https://projects.theforeman.org/issues/34996 from this bug

Comment 5 Bryan Kearney 2022-06-27 16:03:49 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34996 has been resolved.

Comment 6 Vladimír Sedmík 2022-07-12 15:48:39 UTC

It seems the fix was not cherry-picked in 6.12.0 snap 1.0

Comment 9 Vladimír Sedmík 2022-08-31 14:13:12 UTC

Verified in 6.12.0 snap 8:
1) Using a Satellite with HTTP proxy set, the Capsule installation succeeded without any issues.
2) Using setup from 1) there was no regression observed in current coverage for Capsule and Capsule-Content components.
3) Using a 6.11.2 Satellite with HTTP proxy set and Capsule installed (and removed from the proxy except list) the Satellite upgrade succeeded without any issues and the N-1 Capsule was operational.
4) Using setup from 3) the Capsule upgrade succeeded without any issues and the Capsule remained operational.

Comment 13 errata-xmlrpc 2022-11-16 13:32:43 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: Satellite 6.12 Release), 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:8506