Bug 64406

Summary:	disabled service mistakenly starts on preferred node
Product:	Red Hat Enterprise Linux 2.1	Reporter:	Jason Baron <jbaron>
Component:	clumanager	Assignee:	Jason Baron <jbaron>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.1	CC:	knoel
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-05-06 13:36:03 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 Jason Baron 2002-05-03 19:20:49 UTC

Description of Problem:

disabled service mistakenly starts on its preferred node

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


How Reproducible:

create a service preferred to node A. disable it. Restart node B,
then restart node A.

Steps to Reproduce:
1. create a service preferred to node A. Disable it.
2. node B> serivce cluster stop;  node B> service cluster start
3. node A> service cluster stop;  node A> service cluster start

Actual Results:

service is running on node A

Expected Results:

service remains disabled

Additional Information:  Thanks to Michael Waite for finding this

Comment 1 Jason Baron 2002-05-23 18:47:36 UTC

Fixed by causing the relocation of a failed service error out in the service 
manager.