Bug 762404 (GLUSTER-672)

Summary:	While adding a server, aborting does not work well.
Product:	[Retired] GlusterSP	Reporter:	Allen Lu <allen>
Component:	core	Assignee:	Balamurugan Arumugam <bala>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.0.3	CC:	fharshav, platform, shireesh, webteam
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Windows
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Allen Lu 2010-02-22 21:10:22 UTC

If I abort the process on "adding server" by clicking on the 'abort' button, the main server does not abort. Further, the added node reboots. If I want to choose to install as additional node again, everything goes into limbo. Main Server continues to spin the hourglass and added server waits for server manager to take control.

Comment 1 Harshavardhana 2010-03-10 10:38:59 UTC

Right now connection is synchronous and breaking if connection renders no proper notification to Agents. Ejabberd removal in 3.0.5 should resolve this issue.