Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 144954 - Magma arbitrarily chooses cluster infrastructure if multiple are running
Magma arbitrarily chooses cluster infrastructure if multiple are running
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: magma (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Lon Hohberger
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2005-01-12 18:05 EST by Lon Hohberger
Modified: 2009-04-16 16:16 EDT (History)
2 users (show)

See Also:
Fixed In Version: rhcs4u2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-12-06 10:53:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lon Hohberger 2005-01-12 18:05:02 EST
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-13 19:09:39 EST
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 13:49:05 EST
Patches committed to CVS.

Note You need to log in before you can comment on or make changes to this bug.