Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
After removing "HTTP(S) proxy" for all outgoing HTTP connections from Satellite, the satellite is still using it.
2021-02-02T11:16:13 [I|app|c860285b] (RestClient) Proxying request to CAPSULE-FQDN via https://[PROXY IP]:[PROXY PORT]
Version-Release number of selected component (if applicable):
Satellite 6.8.2
How reproducible:
100%
Steps to Reproduce:
1. Set a proxy for all outgoing HTTP connections from Satellite
Satellite webUI -> Administer -> Setting -> General -> HTTP(S) proxy
2. Test the connection with the external capsule by browsing the capsule from the Infrastructure/Capsules page
2021-02-02T11:16:13 [I|app|c860285b] (RestClient) Proxying request to CAPSULE-FQDN via https://[PROXY IP]:[PROXY PORT]
3. Remove the proxy and restart satellite services ,then test the connection with the external capsule again.
Actual results:
The satellite is still using the removed proxy.
2021-02-02T11:16:13 [I|app|c860285b] (RestClient) Proxying request to CAPSULE-FQDN via https://[PROXY IP]:[PROXY PORT]
Expected results:
The removed proxy is not used .
Additional info:
After setting and removing the proxy , the connection to the external capsule can be successful only after adding the capsule FQDN on "HTTP(S) proxy except hosts"
The excerpt from the logs shows the exact same request (same time, same request id) both before and after removing the proxy. Could you provide actual data capturing what is going on?
Also capsule is probably not the right component. No changes we would make to the capsule itself would make Satellite treat http proxies differently.
Requests to capsules are now never proxied, which should resolve this BZ. For details see https://bugzilla.redhat.com/show_bug.cgi?id=1984400 . I'll go ahead and close this as closed-currentrelease as it should be fixed starting with 6.12. If you feel there is still something left to be done, feel free to reopen.