Red Hat Bugzilla – Bug 189777
VIP services do not always get assigned to preferred node on bootup
Last modified: 2009-04-16 16:20:06 EDT
Description of problem: On bootup the VIP services do not always get moved to the preferred node in the failover domain. For instance with a four node cluster with 24 VIP services configured, 3 of the 24 did not get placed on node 3 which was the preferred node for that failover domain. In the attached file Iâve included the syslog messages from node 1 which was up before node 3 but did not move the 3 VIPs to node3 as expected. You will see where node 3 came up and node 1 tried to move the VIPs but failed. There are messages like <warning> #XX: Cancelling relocation: Shutting down. Version-Release number of selected component (if applicable): rgmanager-1.9.46-0 How reproducible: Often but not every time Steps to Reproduce: 1. Create a signficant number of IP services (ie. 24 or more) 2. Create as many ordered, restricted failover domains as there are nodes in the cluster 3. Distribute the IP services over the failover domains so that for a four node cluster, for example, 1/4 of the service get assigned to node 1 first, 1/4 get assigned to node 2 first, etc. 4. Bring up the cluster Actual results: Not all VIP services are assigned to the preferred node in its failover domain Expected results: Every VIP service should be assigned to the preferred node in its failover domain Additional info:
Created attachment 128151 [details] Syslog messages
This should fix this bug and 190234 http://people.redhat.com/lhh/rgmanager-1.9.46-1speed.x86_64.rpm http://people.redhat.com/lhh/rgmanager-1.9.46-1speed.i386.rpm http://people.redhat.com/lhh/rgmanager-1.9.46-1speed.src.rpm
newer packages here: http://people.redhat.com/lhh/rgmanager-1.9.46-1.3speed.x86_64.rpm http://people.redhat.com/lhh/rgmanager-1.9.46-1.3speed.i386.rpm http://people.redhat.com/lhh/rgmanager-1.9.46-1.3speed.src.rpm Let us know if this fixes the behanior.