Bug 2030460

Summary:	Need a way to sync from a specific content view lifecycle environment of the upstream organization
Product:	Red Hat Satellite	Reporter:	Partha Aji <paji>
Component:	Inter Satellite Sync	Assignee:	Partha Aji <paji>
Status:	CLOSED ERRATA	QA Contact:	Radek Mynar <rmynar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	pcreech
Target Milestone:	6.11.0	Keywords:	Regression, 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:31:01 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 Partha Aji 2021-12-08 20:02:41 UTC

Description of problem:
ISS Connected workflow where a Downstream Satellite directly pulls/syncs content from another upstream satellite is now available in the nightly. However it has a a 
restriction. It will only pull from the Default Content View and Library environment in the upstream satellite.

Some customers want the Downstream satellite to only fetch from a content view environment of the Upstream.

This RFE proposes adding the following changes


1) Add a Content View Label and Environment Label to the cdn configurator
2) Handle RH Repository Enablement appropriately. We can either try to figure out if the repository is available in the content view environment of the Upstream sat OR just enable based on if its available in the library or not. (later may lead to bad user experience but better than status quo.)
3) Set the content urls in the RH Repos to include the CV and LCE.

Comment 2 Partha Aji 2021-12-14 01:36:16 UTC

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

Comment 3 Bryan Kearney 2021-12-18 20:06:39 UTC

Upstream bug assigned to paji

Comment 4 Bryan Kearney 2021-12-18 20:06:41 UTC

Upstream bug assigned to paji

Comment 5 Bryan Kearney 2022-01-13 20:05:00 UTC

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

Comment 7 Radek Mynar 2022-06-14 15:17:51 UTC

Satellite can be configured to consume content of specific Lifecycle Environment and specific Content View. Synchronization of that content behaves correctly. Discrepancies are being/were solved in separate issues.

VERIFIED with Satellite 6.11 SNAP 24 @ RHEL8.5

Comment 10 errata-xmlrpc 2022-07-05 14:31:01 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