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.
[RFE]Creating a new HTTP Proxy in satellite GUI should have an option to automatically update/set the "Default HTTP Proxy setting", in the "Administer menu" .
1. Proposed title of this feature request
Creating a new HTTP Proxy in satellite GUI should have an option to automatically update/set the "Default HTTP Proxy setting", no need to navigate to "Administer menu" to update/set global default proxy again.
2. What is the nature and description of the request?
Many organizations utilizing Red Hat Satellite have network policies that block direct access to the internet by the Satellite Server,
and instead require that the Satellite Server go through an HTTP proxy to access the internet to synchronize content.
Currently, to configuring a Global Proxy in Satellite, we have to follow the below steps:-
Satellite WebUI > Infrastructure menu and select HTTP Proxies // Define the proxy details.
Then, he has to configure Satellite to use this newly created proxy as the global default proxy. // Most of the customer missed this step
Steps:-
======
Administer menu, and select Setting > Content tab > Default HTTP Proxy setting > Select the one he created earlier.
3. Why does the customer need this? (List the business requirements here)
In one page the customer can define/update/set the "Default HTTP Proxy setting", since Satellite doesn’t have an HTTP proxy setting at the organization level,
and the Default HTTP Proxy setting is global to all organizations. so manaully again going to Administer menu, and update the "Default HTTP Proxy setting" does not make much sense.
4. How would the customer like to achieve this? (List the functional requirements here)
I am suggesting to put an option in the HTTP Proxies page to update/set the "Default HTTP Proxy setting".
so that customers don't have to navigate to the "Administer menu, and select Setting > Content tab > Default HTTP Proxy setting > content" to update the settings.
5. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Unknown
6. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
No
7. Is the sales team involved in this request and do they have any additional input?
No
8. List any affected packages or components.
Unknown
I will add my point of view here as well which I had mentioned to the reporter of this bug.
1. If someone is creating a proxy they should have an option to set it as the content_default_http_proxy on the same form by use of a checkbox.
2. If someone has created two proxies and has set the first one as content_default_http_proxy , then if he tries to do the same for the second proxy, then a warning should appear saying "<Proxy_Name> is already set as the content_default_http_proxy. Do you want to overwrite this change ?" and Yes\No options should appear.
3. If someone wants to delete a http_proxy and that is set as content_default_http_proxy, delete action should unset the value of content_default_http_proxy as well.
Hi,
I suggest removing the RFE from the 6.16 scope. With the current committed scope and the list of bugs to fix, I doubt the Rocket team will have time to review it.
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.