Red Hat Bugzilla – Bug 64406
disabled service mistakenly starts on preferred node
Last modified: 2013-03-06 00:55:28 EST
Description of Problem:
disabled service mistakenly starts on its preferred node
Version-Release number of selected component (if applicable):
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
service is running on node A
service remains disabled
Additional Information: Thanks to Michael Waite for finding this
Fixed by causing the relocation of a failed service error out in the service