Bug 472909 - [RFE] - Documentation - Conga and Cluster troubleshooting documentation requires content.
Summary: [RFE] - Documentation - Conga and Cluster troubleshooting documentation requi...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: doc
Version: 4
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: John Ha
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-25 15:40 UTC by Stuart R. Kirk
Modified: 2020-03-27 20:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:08:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Stuart R. Kirk 2008-11-25 15:40:40 UTC
Within the Conga and Red Hat Cluster Suite documentation, there are sections pertaining to the troubleshooting of common scenarios users may encounter.  Unfortunately, in both of these guides, the text simply says:

"For information about diagnosing and correcting problems in a cluster, contact an authorized Red hat support representative."

These URLs are:

http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/en-US/RHEL510/Cluster_Administration/s1-admin-problems-conga-CA.html

*and*

http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/en-US/RHEL510/Cluster_Administration/s1-admin-problems-CA.html

Very frequently customers base their decisions on acquiring a new product by the documentation that supports it.  The current state of the troubleshooting documentation does not contain what I believe would make a customer feel confident they would be able to address even a minor issue with a Red Hat cluster.

Comment 2 Stuart R. Kirk 2008-11-25 20:32:42 UTC
Further to this, detailed documentation associated with 3rd party resource monitoring agents like Oracle and SAP that details what is being monitored and what the start/stop/restart functions look like.  Presently the only way to view this information is by dissecting the code located in /usr/share/cluster for details on what each of these scripts are really doing behind-the-scenes.


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