Bug 629152

Summary:	Adding a node to existing cluster with Conga sometimes fails.
Product:	Red Hat Enterprise Linux 5	Reporter:	Wade Mealing <wmealing>
Component:	conga	Assignee:	Ryan McCabe <rmccabe>
Status:	CLOSED DUPLICATE	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.7	CC:	cluster-maint, tao
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-10-26 20:22:06 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 Wade Mealing 2010-09-01 04:58:59 UTC

Description of problem:

According to customer, in RHEL5, adding a new node to existing two node cluster through luci doesn't work properly . The entry for new node is added to cluster.conf of running nodes but on new node, it creates an empty cluster.conf.

Version-Release number of selected component (if applicable):


How reproducible:

Very, very seldom.  I can't reproduce.  Apparently never reproduces with debugging on. 


Steps to Reproduce:
0. Using the web interface (luci)
1. Create a cluster
2. Add a single node
3. Add Another node
  
Actual results:

Sometimes.. (I have tried over 1000 times myself), the node wont be able to be added without having to choose "reboot node" through the interface.

Expected results:

The system never having to reboot.





Additional info:

Comment 5 Ryan McCabe 2010-10-26 20:22:06 UTC


*** This bug has been marked as a duplicate of bug 612300 ***