#1769 IMMSv: Class create and class delete failing with ERR_TRY_AGAIN after failovers

[Chani Srivastava]

Setup:
Changeset- 7436 patched with #1716 and #1748 ticket
OS: SUSE 11SP2 x86_64
2PBE enabled with 20k objects

On invoking failovers, class create and class delete failed with ERR_TRY_AGAIN, on calling 10 times.

Attaching immnd traces.

Snippet from the run

Waiting for FAILOVER to happen04/15/16 12:57:13PM.
100|0| NTFSv utility subscription passed
100|0|Creating a socket...: SUCCESSFUL
100|0|Binding the socket...: SUCCESSFUL
100|0| Portnumber of the client...: 17277
100|0|Sending the REGISTER message to conn_pc ...: SUCCESSFUL
100|0|Receiving the START message...: SUCCESSFUL
100|0|Char from server = START
100|0| Message Received successfully
100|0|fail_over is successfully invoked 04/15/16 12:57:32PM. Invocation of saImmOmClassCreate_2 is successful
100|0|Waiting for FAILOVER to COMPLETE 04/15/16 12:57:33PM.
100|0| failover is successfully completed 04/15/16 12:58:17PM. saImmOmClassDelete Return Value : SA_AIS_ERR_TRY_AGAIN
100|0|
100|0| Try again count : 1
100|0| Try again count : 2
100|0| Try again count : 3
100|0| Try again count : 4
100|0| Try again count : 5
100|0| Try again count : 6
100|0| Try again count : 7
100|0| Try again count : 8
100|0| saImmOmClassDelete Try again count exceeded
100|0| Try again count : 9
100|0| Try again count : 10
100|0| Try again count : 10
100|0| Invocation of saImmOmFinalize is successful

[Neelakanta Reddy]

This is as per design.

In the case of failover, one of the SC(controller will be down) at that time due to data consistency if both PBE are not present imm will not allow the ccb, class create/delete, admin operations. TRY_AGAIN is returned.

There is option given in IMM if one PBE is not there please refer to 2PBE README/PR-guide (osaf/services/saf/immsv/README.2PBE) section "OneSafe2PBE"