Bug 64406 - disabled service mistakenly starts on preferred node
Summary: disabled service mistakenly starts on preferred node
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: clumanager
Version: 2.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Baron
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-05-03 19:20 UTC by Jason Baron
Modified: 2013-03-06 05:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-05-06 13:36:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2002:226 0 normal SHIPPED_LIVE Fixes for clumanager addressing starvation and service hangs 2002-10-08 04:00:00 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.