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 2053842 - The "Serve via HTTP" and "Verify SSL" options in Repo Discovery page does not functions at all in Satellite 7.0
Summary: The "Serve via HTTP" and "Verify SSL" options in Repo Discovery page does not...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.11.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: 6.12.0
Assignee: Chris Roberts
QA Contact: Cole Higgins
URL: https://projects.theforeman.org/issue...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-12 15:54 UTC by Sayan Das
Modified: 2022-11-16 13:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-16 13:33:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34617 0 Normal New The "Serve via HTTP" and "Verify SSL" options in Repo Discovery page does not functions at all in Satellite 7.0 2022-03-15 14:07:57 UTC
Github Katello katello pull 10015 0 None open Fixes #34617 - correct ssl verify param for repo discovery 2022-03-15 14:14:26 UTC
Github Katello katello pull 10169 0 None open Refs #34617 - Remove publish via https 2022-06-17 13:37:54 UTC
Red Hat Issue Tracker SAT-8441 0 None None None 2022-03-15 14:15:23 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:33:44 UTC

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:

NA
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
Note You need to log in before you can comment on or make changes to this bug.