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.

Bug 1395852

Summary: [RFE] Improve Satellite6 documentation by giving an option to the user to see instructions only for rhel 6/rhel7/both
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: DocumentationAssignee: satellite-doc-list
Status: CLOSED WONTFIX QA Contact: satellite-doc-list
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1.8CC: adahms, bkearney
Target Milestone: UnspecifiedKeywords: FutureFeature
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: 2018-02-19 23:31:41 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 sthirugn@redhat.com 2016-11-16 20:09:44 UTC
Description of problem:
Improve Satellite6 documentation by giving an option to the user to see instructions only for rhel 6/rhel7/both

Version-Release number of selected component (if applicable):
Satellite 6.2

How reproducible:
Always

Steps to Reproduce:
1. Go to https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server


Actual results:
Although this comment is applicable to entire Satellite 6 documentation, for easy example, look at this section: - Section 6.2 - Step 12:

"12. Enable the new repository for Red Hat Satellite 6.2.

On Red Hat Enterprise Linux 6, run the following command:

# subscription-manager repos --enable rhel-6-server-satellite-6.2-rpms
On Red Hat Enterprise Linux 7, run the following command:

# subscription-manager repos --enable rhel-7-server-satellite-6.2-rpms"


Expected results:
If I am a customer who have just rhel 7 installations, I should be shown:

"12. Enable the new repository for Red Hat Satellite 6.2.

On Red Hat Enterprise Linux 7, run the following command:

# subscription-manager repos --enable rhel-7-server-satellite-6.2-rpms"


Additional info:
The user should be given an option to select his base OS - say 'rhel6' or 'rhel7' or 'both' in a dropdown - something like https://theforeman.org/plugins/#2.2Packageinstallation

Advantages:
* The user will be shown only the things which are relevant to his base OS.  This will improve readability and hence improve speed of installations.

Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:

Comment 1 Andrew Dahms 2018-02-19 23:31:41 UTC
Hi Sureshkumar,

Thank you for raising this bug.

This has been open for a while now, and I apologize for the long delay in providing an update.

I have now discussed this with our tooling team, and I am afraid this is not something we are able to implement at this stage. As such, I will now be closing this bug, but we are continuing to look into ways we can improve the customer experience with the documentation, and we might be able to find a way to split out instructions this way some time in the future.

I will let you know if we are able to make any advances at some stage.

Kind regards,

Andrew