#2391 IMM: OI should not receive callbacks on a locked node

[Chani Srivastava]

Environment details

OS : Suse 64bit
Changeset : 8701 ( 5.2RC1)
Setup : 4 nodes

Steps to Reproduce:
Create a test class
Node1 - Initialize OM with A.2.18
Node2 - Initialize OI with A.2.18
Node2 - Make OI implementer for the test class created
Node2 - Call OiDispatch
Lock Node2
* Node1 - Try creating an object for test class for which OI is an implementer

OI receives CreateCallback and responds with SA_AIS_OK

Expected: On a clm locked node, OI should not receive any callback when initialize with A.2.18

[Neelakanta Reddy]

From The README:

IMMD is not yet integrated, as the IMMND has to services to clients with lesser versions.
IMMND has to be UP even if the CLM node is down. The IMMD integration has to be done along
with Enhanced cluster management(#439).

since IMMND is up, on the CLM locked node, OI is receiving callback and responds.

From the IMM spec:
When the cluster node leaves the membership, the IMM Service executing on the
remaining nodes of the cluster behaves as if all processes that were using the IMM
Service on the leaving cluster node had been terminated. In particular, if a process on
the leaving cluster node was registered as an Object Implementer, the IMM Service
will unregister it automatically

Following is the observation:

1. since, to service clients with lesser version, IMMND is not down on the node the same has been updated in README.
2. when calling object implementer registered with A.02.18, the callback is allowed as there is no proper return code and implementers are not unregistered.

solution:
when the node is locked, and there are OI registered with A.02.18 with implementers, then these implementers will be unregistered.

[Neelakanta Reddy]

changeset: 8730:50398de4f5bc
tag: tip
user: Neelakanta Reddy reddy.neelakanta@oracle.com
date: Tue Mar 28 11:49:41 2017 +0530
summary: imm:unregister local implementers when clm node is locked[#2391]