Bug 1545000

Summary:	[RFE] As a user of Satellite, I would like to use another Satellite as my CDN.
Product:	Red Hat Satellite	Reporter:	Rich Jerrido <rjerrido>
Component:	Inter Satellite Sync	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Lai <ltran>
Severity:	medium	Docs Contact:
Priority:	high
Version:	Unspecified	CC:	ahumbe, bkearney, ekirby, jpasqual, ktordeur, mmccune, swachira, vmeghana
Target Milestone:	6.11.0	Keywords:	FutureFeature, PrioBumpGSS, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-05 14:27:51 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:
Bug Depends On:
Bug Blocks:	1316897, 1545876

Description Rich Jerrido 2018-02-14 01:26:09 UTC

Description of problem:

Many users due to internal or network requirements, would like the ability to synchronize one Satellite directly from another. 

Today, in Satellite 6.2 and 6.3, we delivered Inter-Satellite-Sync [https://access.redhat.com/articles/2390791] , which allows an administrator to select a Repository, a content view (including the special ‘Default Organization View), and a repository within a content view and export it to disk. This was designed primarily for the disconnected use-case (I have an internet connected Satellite which I use to export content for a disconnected Satellite). 

While this capability can be used to support downstream Satellites, it requires an export of content first (which requires 2x disk space) and the export is a point in time snapshot. (which means that the administrator would have to put processes in place to export content periodically).

Comment 3 Rich Jerrido 2018-07-18 12:38:00 UTC

*** Bug 1362230 has been marked as a duplicate of this bug. ***

Comment 7 Bryan Kearney 2019-09-03 19:06:46 UTC

The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 10 Lai 2022-02-10 20:32:29 UTC

Steps to retest

1. Have 2 satellites: one has host and one as client
=== Host Section ===
2. On the host, upload a manifest, enable the Red Hat Satellite Tools 6.10 for RHEL 8 x86_64 RPMs repo (you can use any)
3. Sync the repo
=== Client section ====
4. On the client, go to content -> Content Credentials and create a certificate for ssl connection.  The certificate will be taken from the host
5. Go to Content -> Subscription -> Manage Manifest -> CDN configuration and fill out the info for connection to the host using the ssl cert that was created
6. Upload a manifest to the client
7. try to enable a repo other than the one in step 2
8. Enable and sync repo in step 2

Expected:
7. Should receive an error saying user cannot enable repo
8. enable and syncing should be successful

Actual
7. Received an error message saying user cannot enable repo
8. enable and syncing is successful

Additionally, if you go to the repo details page on the client, you can see that it's not using CDN as the Upstream URL.  Instead, it's using the url from the host.  This is expected because it's syncing content from the host.

Verified on 7.0 snap 8 with rhel7.9

Comment 15 errata-xmlrpc 2022-07-05 14:27:51 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 (Moderate: Satellite 6.11 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:5498