From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2.1) Gecko/20010901 Description of problem: I configured a samba service on member A and forgot to copy over the smb.conf.sharename file over to member B. (OK, this is a user configuration error.) The service was started up on A, but its preferred member was B. Then when member B joined the cluster, member A stopped the service, assuming that member B would pick it up. Member B was unable to start the service. Consequently the service was left in the disabled state, where it ideally would have been restarted on member A. I would imagine that there may be other scenarios whereby a service is unable to start on one member, but can run on the other. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Detailed above 2. 3. Actual Results: Service outage. Expected Results: Service running on healthy cluster member. Additional info:
The ideal behavior suggested is in the service manager. I tried this same scenario and this ideal behavior was exhibited. Perhaps, more info is needed to reproduce this problem?
Fix in pool.