Bug 669440
| Summary: | Service will failback on "nofailback" failover domain if service is in "starting" state | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Shane Bradley <sbradley> | ||||
| Component: | rgmanager | Assignee: | Lon Hohberger <lhh> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Toure Dunnon <tdunnon> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 5.7 | CC: | cluster-maint, edamato, jruemker, mjuricek, tdunnon | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | rgmanager-2.0.52-10.1.el5 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 672841 (view as bug list) | Environment: | |||||
| Last Closed: | 2011-07-21 10:47:25 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 672841 | ||||||
| Attachments: |
|
||||||
http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=9a4c263b0367fe2d80127e17b94c049e9ee2c59e Posted to STABLE31 Verified in version rgmanager-2.0.52-19.el5, kernel 2.6.18-265.el5
Service in "starting" state on node a2 will not failback when rgmanager is started again on node a1.
<failoverdomain name="failoverdomain1" ordered="1" nofailback="1">
<failoverdomainnode name="a1" priority="1"/>
<failoverdomainnode name="a2" priority="2"/>
<failoverdomainnode name="a3" priority="3"/>
</failoverdomain>
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-1000.html |
Created attachment 473374 [details] Patch that will fix issue with failback service if in "starting" state Description of problem: If a failover domain has "nofailback" enabled a service that is "starting" state would still failback to the original. If a service takes a while to come up and is in the "starting" state and the original node comes back online while it is in that state the service will be failed back. There is patch attached that resolves this issue. Version-Release number of selected component (if applicable): rgmanager-2.0.52-9.el5 How reproducible: Everytime Steps to Reproduce: 1. Start a service on NodeA which is failover domain X that has "nofailback, ordered" enabled. In order to recreate the service needs to spin for a few seconds so that is in "starting" for x seconds. 2. stop rgmanager on NodeA 3. Watch logs on NodeB and start rgmanager on NodeA once NodeB starts the failed over service. Actual results: Service will failback Expected results: Service should not failback Additional info: