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:
Satellite can be configured to use content from upstream Satellite - Network Sync. By default it pulls content from Library/Default_Organization_View. It can be also configured to pull content from specified Lifecycle Environment and Content View. This CDN configuration is visible in UI but in CLI (hammer organization info -> CDN configuration) LCE and CV are not visible.
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. prepare an upstream satellite with organization, lifecycle environment and content view
2. configure downstream to use specified LCE and CV from upstream server
3. run "hammer organization info --name <downstream org>"
Actual results:
CDN configuration:
URL: https://<upstream_server>/
Upstream Organization: <ExportOrg>
Username: <username>
SSL CA Credential ID: 1
Expected results:
Output should include also LCE label, and CV label
Additional info:
Both values are configurable using "hammer organization configure-cdn ... (--upstream-lifecycle-environment-label | --upstream-content-view-label)" and also via UI, where both are visible.
VERIFIED
satellite-6.12.0-3.el8sat.noarch
foreman-3.3.0.8-1.el8sat.noarch
I have followed the steps in Comment0 and now hammer is showing LCE and CV in "hammer organization info --name <downstream org>" output.
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
Description of problem: Satellite can be configured to use content from upstream Satellite - Network Sync. By default it pulls content from Library/Default_Organization_View. It can be also configured to pull content from specified Lifecycle Environment and Content View. This CDN configuration is visible in UI but in CLI (hammer organization info -> CDN configuration) LCE and CV are not visible. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. prepare an upstream satellite with organization, lifecycle environment and content view 2. configure downstream to use specified LCE and CV from upstream server 3. run "hammer organization info --name <downstream org>" Actual results: CDN configuration: URL: https://<upstream_server>/ Upstream Organization: <ExportOrg> Username: <username> SSL CA Credential ID: 1 Expected results: Output should include also LCE label, and CV label Additional info: Both values are configurable using "hammer organization configure-cdn ... (--upstream-lifecycle-environment-label | --upstream-content-view-label)" and also via UI, where both are visible.