This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2151536 - Removing an organization from a HTTP proxy can leave the proxy as the Default HTTP Proxy in Settings
Summary: Removing an organization from a HTTP proxy can leave the proxy as the Default...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: HTTP Proxy
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-07 13:21 UTC by Pavel Moravec
Modified: 2024-06-06 12:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 12:56:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-25425 0 None Migrated None 2024-06-06 12:55:59 UTC

Description Pavel Moravec 2022-12-07 13:21:16 UTC 
Description of problem:
See reproducer.


Version-Release number of selected component (if applicable):
Sat 6.12 (or any older)


How reproducible:
100%


Steps to Reproduce:
1. Create 2 organizations and a HTPP Proxy, assigned to both Orgs.
2. Set the proxy as the Default HTTP Proxy in the Settings
3. Edit the proxy to disassociate it from one Organization.
4. For this Org:
  4a. check its Settings -> Content -> Default HTTP Proxy
  4b. create a repo and attempt to sync it.


Actual results:
4a shows this organization (not further associated with the proxy) has (global) setting refering to the proxy. One can not newly set the proxy (which is good), but already set proxy remained set, which is the wrong.
4b repo sync attempts to use the proxy, despite it is disassociated for the Organization that created the repository.


Expected results:
The step 3 should reset the global Settings to no proxy - or rpevent the disassociation or warn a user about a misconfig


Additional info:
There is a schism where:
- HTTP Proxies can be configured per (or associated with) Organization
- Global HTTP Proxy is a global settings applicable to all Organizations

Ideal solution would be to resolve this schism in either way. Since we should allow different proxies for different organizations, this would mean Settings to be scoped by Organization..?
Comment 1 Eric Helms 2024-06-06 12:56:00 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.
Note You need to log in before you can comment on or make changes to this bug.