Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1694722 - Need release note and entry in the Managing Hosts guide outlining support for RHEL8 for Satellite 6.5
Summary: Need release note and entry in the Managing Hosts guide outlining support for...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Documentation
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: satellite-doc-list
QA Contact: satellite-doc-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-01 13:18 UTC by Rich Jerrido
Modified: 2019-04-01 13:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Rich Jerrido 2019-04-01 13:18:43 UTC
We will only support RHEL8 as a client of Satellite 6.5. 

Previous releases of Satellite will not support RHEL8, nor will we deliver the Satellite tools repositories to those older versions of Satellite. 

running a RHEL8 client with any version of Satellite that isn't Satellite 6.5 or newer is (and will be) an unsupported configuration

This needs to be called out in the Release Notes and other documentation (Install Guide / Managing hosts guide) VERY prominently

Comment 2 dvoss 2019-04-01 13:44:21 UTC
Hi Melanie,
Can you help me understand the documentation impact of this issue? For example, Rich calls out two documents, but can you think of any others that may be impacted?

Comment 3 Melanie Corr 2019-04-01 13:55:06 UTC
Hi David, 

Creating a RHEL 8 machine in Satellite affects procedures in Content Management Guide for repositories. All the other procedures stay the same because it is the exact same process to create. From a documentation perspective, I don't think we need to litter the docs with info that it is only supported in 6.5. If we do that, then we'd have to do it for everything. That should be called out in the Release Notes. If we extend this logic, we would have to pepper all docs with info about what is supported in x version and not in y. Then we would have to backport to earlier doc versions with this level of info too, for all features.  Doesn't make sense. We can say in the release notes that it is supported in 6.5 only.


Note You need to log in before you can comment on or make changes to this bug.