Bug 227232
Summary: | Services are starting after machine reboot (rgmanager restart) | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Tomasz Jaszowski <tjaszowski> |
Component: | rgmanager | Assignee: | Lon Hohberger <lhh> |
Status: | CLOSED WONTFIX | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | cluster-maint, michael.hagmann |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-07-29 18:34:20 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
Tomasz Jaszowski
2007-02-03 19:47:04 UTC
What rgmanager package do you have? - rgmanager-1.9.54-1 Ok, so, in your test case, you are never rebooting the other node, or shutting rgmanager down, right... If this is the case, then what you are seeing is correct/expected behavior. The other node has the state recorded as 'stopped'. Whenever a membership transition occurs, services are evaluated to see if the a node (presumably the new node) is capable of running any service in the 'stopped' state. If so, then the service is started. 'Autostart' is for cluster quorum transitions, or total rgmanager group transitions. Since the surviving node maintains the cluster quorum (and rgmanager is still running), the "enabled" vs "disabled" state is not reset. What we can do is provide an option to disable a service at the point no nodes are capable of running it. For example, in your case, only one node is capable of running the service. When it is offline (or rgmanager is down), the other node could then mark the service as 'disabled' automatically - because it knows that: (a) No nodes are capable of running the service, and (b) the administrator wants the service disabled if (a) occurs. Note that rgmanager does stop-before-start - so your stop scripts should be able to clean up any problems that exist prior to the service starting. If that's not the case (and you want manual intervention prior to service start), you can disable rgmanager on boot: chkconfig --del rgmanager Need to reopen this momentarily for housekeeping |