Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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.
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
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