Bug 1820193

Summary:	Deleted Global Http Proxy is still being used during repository sync.
Product:	Red Hat Satellite	Reporter:	Jameer Pathan <jpathan>
Component:	Repositories	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Jameer Pathan <jpathan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.7.0	CC:	jjeffers, pcreech
Target Milestone:	6.8.0	Keywords:	Triaged
Target Release:	Unused	Flags:	jjeffers: needinfo-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-3.16.0-0.14.rc3.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 13:01:14 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 Jameer Pathan 2020-04-02 13:46:38 UTC

Description of problem:
Deleted Global Http Proxy is still being used during repository sync.

Version-Release number of selected component (if applicable):
- Satellite 6.7.0 snap 17

How reproducible:
Always

Steps to Reproduce:
1. Create Http Proxy (Go to Infrastructure > Http Proxies > New Http Proxy)
2. Set the created proxy as Default Http Proxy( Go to Administer > content > Default HTTP Proxy)
3. Create repository with Global Default Http Proxy.
4. Delete the Http Proxy

Actual results:
- Repository details page still shows the deleted global default Http Proxy.
- Default Http Proxy field on settings page is Empty.
- While creating new proxy, it still shows old deleted Http proxy as Global Default proxy.

Expected results:
- Repository details page shouldn't shows the deleted global default Http Proxy.
- Default Http Proxy field on settings page should be set to no global defult.
- While creating new proxy, it shouldn't shows old deleted Http proxy as Global Default proxy.


Additional info:
- Workaround for this issue:
Edit Default Http proxy field in settings, assign a Http proxy or set it as no global default.

Comment 4 James Jeffers 2020-06-15 11:50:56 UTC

Connecting redmine issue https://projects.theforeman.org/issues/30100 from this bug

Comment 5 Bryan Kearney 2020-06-19 16:02:33 UTC

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

Comment 9 James Jeffers 2020-07-20 13:44:03 UTC

I believe the decision to default to "Global Default (none)" instead of "no proxy" was made because creating a new repository also uses the default value of "use the global proxy" even when there is no global HTTP Proxy set.

In that case, the upstream description is incorrect/misleading, and I apologize for the confusion.

I'm still going to check with Justin and see if thinks this is still the best option.

Comment 11 James Jeffers 2020-07-21 14:23:27 UTC

Jameer,

Justin is out today, I won't be able to query him. I would say, go ahead and mark as verified. I will bring up your observation to the team, and we'll likely add a tracker for discussion about it on our backlog.

Thanks!

Comment 12 Bryan Kearney 2020-07-21 16:02:47 UTC

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

Comment 14 Jameer Pathan 2020-07-22 11:57:38 UTC

Verified:

Verified with:
- Satellite 6.8.0 snap 9

Test steps:
1. Create Http Proxy (Go to Infrastructure > Http Proxies > New Http Proxy)
2. Set the created proxy as Default Http Proxy( Go to Administer > content > Default HTTP Proxy)
3. Create repository with Global Default Http Proxy.
4. Delete the Http Proxy

Observation:
- after deleting global Http proxy, the global default setting value changes to "no global default" and
 repositories those were set to use the global default http proxy reset to "Global Default (None)"

Comment 17 errata-xmlrpc 2020-10-27 13:01:14 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.8 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-2020:4366