Bug 690191 - Service with highest exclusive prio should be relocated to another node with lower exclusive prio
Summary: Service with highest exclusive prio should be relocated to another node with ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rgmanager
Version: 6.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Lon Hohberger
QA Contact: Cluster QE
URL:
Whiteboard:
: 692627 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-23 14:39 UTC by Lon Hohberger
Modified: 2011-12-06 11:57 UTC (History)
7 users (show)

Fixed In Version: rgmanager-3.0.12.1-2.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 680256
Environment:
Last Closed: 2011-12-06 11:57:22 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1595 0 normal SHIPPED_LIVE rgmanager bug fix and enhancement update 2011-12-06 00:38:45 UTC

Comment 1 Lon Hohberger 2011-03-31 18:20:48 UTC 
*** Bug 692627 has been marked as a duplicate of this bug. ***
Comment 2 Lon Hohberger 2011-03-31 18:21:41 UTC 
Description of problem:

A two node cluster each running an exclusive service. The node rh51 is running
the service demoProd(exclusive=1) and the node rh52 is running the service
demoDevel(exclusive=2). The service demoProd fails a status check. Then it
tries to restart the service on the node rh51(itself). Then service demoProd is
stopped successfully. Then node rh51 fails to start the service demoProd. The
service then is migrated to the "stopped" state.
Comment 4 Lon Hohberger 2011-07-08 16:52:55 UTC 
Patch merged to RHEL6 branch from STABLE31; already tested in RHEL57 branch:

http://git.fedorahosted.org/git?p=cluster.git;a=commit;h=2cf74b34240e5830c49ecd1da7ce63f92026a2e4
Comment 7 errata-xmlrpc 2011-12-06 11:57:22 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1595.html
Note You need to log in before you can comment on or make changes to this bug.