Bug 1035969

Summary: Wrong information on selecting base channel for kickstart
Product: Red Hat Satellite 5 Reporter: Sharuzzaman Ahmat Raslan <sharuzzaman>
Component: Docs Getting Started GuideAssignee: Dan Macpherson <dmacpher>
Status: CLOSED CURRENTRELEASE QA Contact: Dan Macpherson <dmacpher>
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedKeywords: Triaged
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-21 02:03:06 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:
Bug Depends On:    
Bug Blocks: 1018166    
Attachments:
Description Flags
screenshot of the wrong information none

Description Sharuzzaman Ahmat Raslan 2013-11-29 04:25:38 UTC
Created attachment 830471 [details]
screenshot of the wrong information

Description of problem:

On page 49 of the Getting Started guide, under section 3.1.2.2, procedure 3.1:

--quote--
For example, to use Red Hat Enterprise Linux 5 with x86 architecture, the rhel-x86_64-server-6 channel and its corresponding Red Hat Network Tools channel rhn-tools-rhelx86_64-server-6 are required.
--quote--

It is not correct to refer RHEL 5 with x86 architecture to RHEL 6 x86_64 channel and also rhn-tools x86_64 channel


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

Edition 2

How reproducible:
Always

Steps to Reproduce:
1. Download Red_Hat_Satellite-5.6-Getting_Started_Guide-en-US.pdf
2. Open the PDF in PDF viewer
3. Go to page 49

Actual results:
Wrong information

Expected results:
Either RHEL 5 x86 should be change to RHEL 6 x86_64, or the channel referred should be changed to RHEL 5 x86 base channel, and rhn-tools x86

Additional info:

Comment 1 sachua 2013-12-05 05:43:44 UTC
Thanks for bringing this to our attention. We will make the amendment with the next doc update.

Comment 2 Dan Macpherson 2014-01-21 15:20:11 UTC
This bug can be worked on early during the planning stages for Satellite 5.7.