Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 144954

Summary:	Magma arbitrarily chooses cluster infrastructure if multiple are running
Product:	[Retired] Red Hat Cluster Suite	Reporter:	Lon Hohberger <lhh>
Component:	magma	Assignee:	Lon Hohberger <lhh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Cluster QE <mspqa-list>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4	CC:	amanthei, cluster-maint
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	rhcs4u2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-12-06 15:53:56 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 Lon Hohberger 2005-01-12 23:05:02 UTC

Description of problem:

Magma picks the first cluster infrastructure it can connect to when
initializing.  If two cluster infrastructures are running, then it
will choose the first from the readdir() operation.

While this is a 100% unsupported use case, it is thought that we may
want to protect against this particular situation.

Possible options:
(1) Simplest:
- List plugins in /etc/cluster/magma.conf with full path.  Only try
listed plugins.

(2) A bit more complex:
- Assign priorities to magma plugins.

Comment 2 Lon Hohberger 2005-01-14 00:09:39 UTC

This will be fixed in the following manner, given that this is
configuration unsupported:

(1) Magma will sort the directory entries by name, and try to load
them in alphabetical order (case-sensitive).  Thus, gulm.so will be
tried before sm.so.  It is not neccesary to weigh one infrastructure
over another.

(2) Any file not having the "S_IRUSR" mode bit set will be ignored. 
This is useful for testing.

Comment 3 Lon Hohberger 2005-01-17 18:49:05 UTC

Patches committed to CVS.