Bug 174020

Summary:	s-c-cluster allows propagation of cluster.conf with only one node configured
Product:	[Retired] Red Hat Cluster Suite	Reporter:	Stanko Kupcevic <kupcevic>
Component:	redhat-config-cluster	Assignee:	Jim Parsons <jparsons>
Status:	CLOSED NOTABUG	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	cluster-maint
Target Milestone:	---
Target Release:	---
Hardware:	noarch
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-05-16 20:33:53 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 Stanko Kupcevic 2005-11-23 19:07:51 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050921 Red Hat/1.0.7-1.4.1 Firefox/1.0.7

Description of problem:
It also allows propagation of 2 node gulm cluster.conf

Version-Release number of selected component (if applicable):
system-config-cluster 1.0.12-1.0

How reproducible:
Always

Steps to Reproduce:
1. Start s-c-cluster on a node of running cluster
2. Remove other nodes
3. Click "send to cluster"
  

Actual Results:  cluster.conf gets propagated

Expected Results:  s-c-cluster should either disallow propagation or pop-up a warning

Additional info:

Comment 1 Jim Parsons 2006-05-16 20:33:53 UTC

This does not seem like a bug - one node clusters are COOL!