Bug 169139

Summary: Cluster hangs due to name length restriction
Product: [Retired] Red Hat Cluster Suite Reporter: Wendy Cheng <nobody+wcheng>
Component: redhat-config-clusterAssignee: Jim Parsons <jparsons>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: cluster-maint, tao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2006-0198 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-09 19:50:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Wendy Cheng 2005-09-23 15:28:43 UTC
+++ This bug was initially created as a clone of Bug #169136 +++ - filed to ask
for sanity check cluster name length in system-config-cluster GUI. 

Description of problem:
Red Hat GPS engineer on-site with customer reported cluster hung. The issue was
solved by restricting max cluster name to 15 characters.  

From: Nicholas Strugnell (nstrug)

Two bugzillas required:
1. Better documentation. The docs are particularly weak addressing how to get
the cluster manager started on the 2nd (and 3rd and 4th...) nodes after running
system-config-cluster on the 1st node. The 15 char limit also needs to be doc'd.
2. Need proper sanity checks in system-config-cluster, ccs_tool etc. to stop us
starting a cluster with too big a name.

Version-Release number of selected component (if applicable):
RHCS cluster on RHEL4U1

Additional info:
1) Patrick Caulfield has enforced "cman_tool join" to sanity checks the cluster
name (code into cvs already). 
2) The bugzilla was cloned to ask "system-config-cluster" sanity check the
cluster name length.

Comment 1 Jim Parsons 2005-11-01 13:56:10 UTC
Fixed in 1.0.17-1.0

Comment 3 Red Hat Bugzilla 2006-03-09 19:50:23 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2006-0198.html