Bug 2053842

Summary:	The "Serve via HTTP" and "Verify SSL" options in Repo Discovery page does not functions at all in Satellite 7.0
Product:	Red Hat Satellite	Reporter:	Sayan Das <saydas>
Component:	Repositories	Assignee:	Chris Roberts <chrobert>
Status:	CLOSED ERRATA	QA Contact:	Cole Higgins <chiggins>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	chrobert, ehelms, sajha, zhunting
Target Milestone:	6.12.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	All
URL:	https://projects.theforeman.org/issues/34617
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-16 13:33:25 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 Sayan Das 2022-02-12 15:54:23 UTC

Description of problem:

The "Serve via HTTP" and "Verify SSL" options in Repo Discovery page does not function at all in Satellite 7.0

Version-Release number of selected component (if applicable):

Satellite 7.0 (satellite-7.0.0-0.4.1.beta.el7sat.noarch)

How reproducible:

Always

Steps to Reproduce:
1. Install RHEL 7 + Satellite 7.0

2. Go to Repo Discovery page, Fill up : Repository Type and URL to Discover and then click on "Discover".

3. Select the discovered repo and click on "Create Selected"

4. Note down the settings\selections of "Serve via HTTP" and "Verify SSL"

5. Mention Repo name\label, select product and then "Run Repository Creation"

6. Check on the newly created repo

Actual results:

At Step 4:, Both of these options are selected whether we keep them selected or unselected them, that does not matters at all.

"Serve via HTTP" | "Verify SSL"

At Step 6, Anyway, the repo will be created in this way :

Verify SSL: Yes
Publish via HTTPS: Yes
Unprotected : No

And the "Published AT" URL is a https URL.

This means, that

A) Those two options during repo discovery served no function.

B) With "Publish via HTTPS: Yes" and "Unprotected : No" , The repo can only be accessed by authenticating via correct CA certificate over https.

C) There is no way to modify "Publish via HTTPS" setting. So providing "Publish via HTTPS" option during Repo Discovery is just meaningless.

Expected results:

* Either replace "Publish via HTTPS" with "Unprotected" and make it functional or else remove the "Publish via HTTPS" choice completely.

* Ensure that the "Verify SSL:" choice is working fine.

Additional info:

Comment 1 Brad Buckingham 2022-02-14 14:34:50 UTC

Is this a regression from Satellite 6.10?

Comment 2 Sayan Das 2022-02-14 15:53:56 UTC

Hello Brad,

Thanks for reaching out. Let me explain a bit.

Starting from Satellite 6.6, One of those options never really worked. 

I had filed this BZ 1789848 back during that time and It was later closed as WONTFIX.

But the situation is a bit different now.

A) Verify SSL never worked and does not work now as well.

B) Till Satellite 6.10, The other option was "Publish via HTTP" and we could select it there as well as edit it at repository level based on which a repo can be either published over HTTP or HTTPS.


   On Satellite 7.0, The flag is changed to "Publish via HTTPS" and by default for all repos It is Enabled and it cannot be modified at repo level, no wonder it does not work on the Discovery page as it's kind of a locked option.

   At the repo level, the "Unprotected" option has been introduced which can be further used to control the behavior of HTTP vs HTTPS based access of the repo. So It makes much more sense to have this option available on the "Repo Discovery" page rather than having the "Publish via HTTPS" option which is unchangeable and always set to true. 


I hope this clarifies the intention of opening this BZ.



BR, 

Sayan

Comment 3 Sayan Das 2022-03-02 18:54:33 UTC

In Snap 10 of Satellite 7.0, 

* The "Serve via HTTP" option is no longer there in the Discovery page for yum repos. So this is already fixed now. 

* Even after we unselect "Verify SSL" option in the discovery page, This remains enabled after the repo gets created. So this needs to be fixed.

* The repo being created has "Unprotected" set to Yes. If that is the expected value, then good or else, I guess, a repo should not be by default marked as Unprotected.

Comment 10 Bryan Kearney 2022-06-17 00:04:50 UTC

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

Comment 11 Bryan Kearney 2022-06-17 16:04:24 UTC

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

Comment 17 errata-xmlrpc 2022-11-16 13:33:25 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.12 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-2022:8506