[Pacemaker] Group not started/stopped in correct order with -INF collocation

[Florian Haas]

On 2011-05-31 16:04, Kulovits Christian - OS ITSC wrote:
> Sorry!! Yes, of course
> 
> 	Corosync Cluster Engine, version '1.2.7' SVN revision '3008'
> 	CRM Version: 1.0.9 (da7075976b5ff0bee71074385f8fd02f296ec8a3)
> 	pacemaker 1.0.10-1.2.el5 - (none) x86_64
> 	corosync 1.2.7-1.1.el5 - (none) x86_64
> 	heartbeat 3.0.3-2.3.el5 - (none) x86_64
> 
> 	Platform: Linux
> 	Kernel release: 2.6.18-164.el5
> 	Architecture: x86_64
> 	Distribution: Description:	Red Hat Enterprise Linux Server release 5.4 (Tikanga)
> 
> You can find the report here: http://dl.dropbox.com/u/30915505/AMOSreport.tar.bz2
> And it is a 4-node cluster...

# CIB_file=cib.xml crm configure show | grep -c -E ^location
35
# CIB_file=cib.xml crm configure show | grep -c -E ^order
40
# CIB_file=cib.xml crm configure show | grep -c -E ^colocation
29
# CIB_file=cib.xml crm configure show | grep -c -E ^primitive
71

Sorry, a CIB with 35 location, 40 order, and 29 colocation constraints,
and 71 resources, is beyond what I am able to troubleshoot without
actually logging on to the box affected. :)

Cheers,
Florian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110601/1f0afa98/attachment-0003.sig>