Bug 126562 - client config guide, specify that the AS bootstrap script is for RHEL 2.1
Summary: client config guide, specify that the AS bootstrap script is for RHEL 2.1
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Documentation
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Clay Murphy
QA Contact: Fanny Augustin
URL: https://rhn.redhat.com/help/client-co...
Whiteboard:
Depends On:
Blocks: 128275
TreeView+ depends on / blocked
 
Reported: 2004-06-23 10:18 UTC by Patrick C. F. Ernzer
Modified: 2009-08-20 03:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-15 14:37:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Patrick C. F. Ernzer 2004-06-23 10:18:48 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
'Chapter 6. Using the Bootstrap Script' states 'Note that systems
running Red Hat Enterprise Linux AS 2.1 or versions of Red Hat Linux
prior to 8.0 should use the script labeled "AS." Refer to the Appendix
A Sample Bootstrap Script for an example script:'

This should read 'Note that systems running Red Hat Enterprise Linux
2.1 or versions of Red Hat Linux prior to 8.0 should use the script
labeled "AS." Refer to the Appendix A Sample Bootstrap Script for an
example script:'

I just had a customer calling as he was trying to use the newer
bootstrap script on RHEL 2.1 ES. His logic was that ES 2.1 is not AS
2.1 and that the docs led him to believe that this meant he needed to
run the newer bootstrap script

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


How reproducible:
Always

Steps to Reproduce:
1. try to register existing systems via bootstrap
2. system is RHEL 2.1 ES
3. read docs
    

Actual Results:  wrong choice of bootstrap scrip

Expected Results:  clear statement in the docs

Additional info:

Comment 1 Clay Murphy 2004-06-23 19:19:33 UTC
Yeah, wow, good catch there Patrick. I should've caught this myself on
the initial write-up. Although the script is labeled AS, and all new
Sats. must run on AS, our clients can be any flavor. Dunno what I was
thinking.

Tell your customer sorry for me; I'll get this fixed in the next
release. Aligning to the 350 doc tracking bug, setting the version to
350, and marking customer facing.

Comment 2 Clay Murphy 2004-07-21 01:38:38 UTC
Moving blocker from the 350 hosted doc bug to the 350 sat doc bug,
since that is when this documentation change will appear.

Comment 3 Clay Murphy 2004-08-10 00:50:45 UTC
This change has been made.

Comment 4 Fanny Augustin 2004-08-12 15:59:33 UTC
Looks good on QA.


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