Bug 707568 - Non existing rhn-tools-rhel-5-i386 referred in the documentation
Summary: Non existing rhn-tools-rhel-5-i386 referred in the documentation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Docs Reference Guide
Version: 541
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lana Brindley
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: sat54-docs
TreeView+ depends on / blocked
 
Reported: 2011-05-25 12:12 UTC by Šimon Lukašík
Modified: 2013-10-23 23:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-29 21:09:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Šimon Lukašík 2011-05-25 12:12:18 UTC 
Description of problem:
Channel rhn-tools-rhel-5-i386 does not exists, but it's referred from
documentation in the chapter: 10. Virtualization. 

On the other hand, we have to note here, that rhn-tools-rhel-4-i386
does exist. And we may want to have it documented.

Please decide if you want to remove that channel. Or include separate 
section for rhel4.


Version-Release number of selected component (if applicable):
RHN Satellite 5.4.1 Reference Guide
RHN Satellite 5.4.0 Reference Guide
Comment 2 Lana Brindley 2011-06-13 20:14:00 UTC 
Slated for 5.4.2.

LKB
Comment 3 Lana Brindley 2011-09-22 20:43:06 UTC 
Šimon, can you please clarify what changes you require here?

Is rhn-tools-rhel-4-i386 the correct channel to obtain RHN Tools, or is there a different channel we should be advising our customers to use?

LKB
Comment 4 Šimon Lukašík 2011-09-23 11:17:25 UTC 
Well, the rhn-tools-rhel-4-i386 is the correct one. However, channel named
rhn-tools-rhel-5-i386 (note digit 5) has never exist.

The line, which reads:

    RHN Tools — rhn-tools-rhel-5-i386 

is wrong and in fact redundant to the previous one. Please remove it.
Comment 5 Lana Brindley 2012-01-04 00:46:46 UTC 
Removed.

Revision 2-5

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