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.

Bug 2227844

Summary: [RFE] Add noproxy option to global registration when running the curl commands
Product: Red Hat Satellite Reporter: Paul Dudley <pdudley>
Component: RegistrationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.13.3CC: ahumbe, dsinglet, gtalreja, lstejska, nalfassi, rlavi
Target Milestone: UnspecifiedKeywords: FutureFeature, MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:25:42 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 Paul Dudley 2023-07-31 16:20:36 UTC
Description of request;

Add an optional field in registration to add a --noproxy to pass to the curl commands so that any proxy defined in system env variables are ignored when going to the Satellite or other URL provided.

Comment 1 Leos Stejskal 2023-08-02 10:34:31 UTC
Can you please describe more in detail how the registration should behave?

Comment 2 Marek Hulan 2023-08-03 13:18:22 UTC
I guess that may require "Ignore system proxy configuration" checkbox. If checked, it would pass this --noproxy to all curl commands used during the registration template.

Comment 3 Paul Dudley 2023-08-03 16:33:55 UTC
Hi Leos, Marek,

Right, that's the idea, to add a checkbox that will be optional that, when checked, will add the --noproxy option on the curl command(s) in the registration template. The template can be customized to add this at the moment, but having the option built in will be convenient for the customer.

I believe this can be a simple checkbox that automatically passes the @rhsm_url.host to --noproxy, but there are perhaps other more convenient ways of doing it.

This assume the scenario of the following;
The user has an environment where systems need a proxy for outside contact, so the proxy env variables are always set. They do not need the proxy to reach the Satellite, so during normal registration these vars get in the way. Adding an optional checkbox to pass --noproxy <registration host> to the curl command will help prevent users from having to edit the curl during each generation of the command, or altering the template themselves for only this purpose.

Comment 4 Eric Helms 2024-06-06 16:25:42 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.