Bug 157365

Summary: magma_gulm.so doesn't detect membership down events
Product: [Retired] Red Hat Cluster Suite Reporter: Lon Hohberger <lhh>
Component: magma-pluginsAssignee: Lon Hohberger <lhh>
Status: CLOSED CURRENTRELEASE QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: medium    
Version: 4CC: 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:54:46 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-05-10 22:37:40 UTC
Description of problem:

The old libgulm used to specifically pass three events:
- Node expired
- Node fenced
- Node logged out

We were waiting for "logged out" messages from gulm core on a node for
membership transitions, but unfortunately, they're no longer delivered if the
node was fenced.  So, magma wasn't correctly membership-down transitions on libgulm.

Fixed in CVS.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Lon Hohberger 2005-05-10 22:44:32 UTC
Fixed in CVS.  This is a fairly huge problem.