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.
Document URL:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html-single/installation_guide/#system_requirements
Section Number and Name:
2.1. System Requirements
Describe the issue:
The current document describes the underlying OS as "Red Hat Enterprise Linux 7 Server".
A customer following a Standard Operating Environment approach requires more information, like a detailed mapping of Satellite zStreams to RHEL zStreams and RHSCL versions.
Suggestions for improvement:
Document the QAd combination of Satellite zStream, RHEL zStream and RHSCL versions.
Additional information:
Hi Stephen,
I agree that guides are too slow to keep this info up to date, and in conversations with support they're concerned about "pinning" versions together in a customer environment. I'm also concerned about who will be responsible for testing these combinations and on what schedule.
Due to these concerns I'm moving this to 6.5 to give us time to look at engineering solutions to pinning z-stream versions together.