Bug 1651242 - Satellite 6 should expose suse client repos via http
Summary: Satellite 6 should expose suse client repos via http
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
high vote
Target Milestone: 6.5.0
Assignee: Partha Aji
QA Contact: jcallaha
Depends On:
TreeView+ depends on / blocked
Reported: 2018-11-19 14:07 UTC by Justin Sherrill
Modified: 2019-11-05 22:38 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-katello-,tfm-rubygem-katello-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-05-14 12:38:54 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 25667 0 Normal Closed Should expose suse client repos via http 2020-08-20 15:22:55 UTC
Red Hat Product Errata RHSA-2019:1222 0 None None None 2019-05-14 12:39:02 UTC

Description Justin Sherrill 2018-11-19 14:07:10 UTC
Description of problem:

Soon sles client repos will be exposed via the cdn, and they need to be accessed in an unprotected manner (currently via http).  The proposed method of doing that is simply checking for a content type of yum and the presence of sles in the url.

Comment 3 Partha Aji 2018-12-11 21:59:05 UTC
Connecting redmine issue https://projects.theforeman.org/issues/25667 from this bug

Comment 4 Satellite Program 2018-12-14 05:06:38 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25667 has been resolved.

Comment 9 jcallaha 2019-02-12 21:09:29 UTC
Moving to Verified as the customer has agreed to verify this locally.
If an issue arises later, this bug can be reopened.

Comment 11 errata-xmlrpc 2019-05-14 12:38:54 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.