Bug 992976

Summary: Documentation-cluster outdated luci setup info
Product: Red Hat Enterprise Linux 5 Reporter: Patrik Hagara <phagara>
Component: doc-Cluster_AdministrationAssignee: John Ha <jha>
Status: CLOSED WONTFIX QA Contact: ecs-bugs
Severity: low Docs Contact:
Priority: low    
Version: 5.10CC: adstrong, phagara
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-02 13:05:08 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 Patrik Hagara 2013-08-05 10:45:11 UTC
Description of problem:

In section 3.2 of Cluster_Administration(EN)-5 (2013-1-4T15:52) guide, there's outdated information on how to initialize luci server (luci_admin binary not present in package). The correct steps should be to login via the luci web interface as user "root" with the associated password.

Also, section 3.3 states (in step 3) to use the root password for each node. This is not true, as one is supposed to enter the ricci password (needs to be set up beforehand on each node with "passwd ricci").


Version-Release number of selected component (if applicable):
Cluster_Administration(EN)-5 (2013-1-4T15:52)

Comment 1 RHEL Program Management 2014-03-07 12:41:48 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 2 RHEL Program Management 2014-06-02 13:05:08 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).