Bug 169139 - Cluster hangs due to name length restriction
Cluster hangs due to name length restriction
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: redhat-config-cluster (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jim Parsons
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2005-09-23 11:28 EDT by Wendy Cheng
Modified: 2009-04-16 16:10 EDT (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2006-0198
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-09 14:50:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Wendy Cheng 2005-09-23 11:28:43 EDT
+++ 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@redhat.com)

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 08:56:10 EST
Fixed in 1.0.17-1.0
Comment 3 Red Hat Bugzilla 2006-03-09 14:50:23 EST
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.


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