#1777 CLM : Admin state attrib of payload CLM object toggles after every switchover

[Srikanth R]

Changeset: 7438
Opensaf version : 5.0.FC
Setup : 5 nodes with 3 payloads.

Issue : CLM Admin state attribute of payload toggles after every switchover

Steps performed :

• All the nodes are brought up initially.
• Continuous Switchovers are triggered.
• When SC-1 just became active , CLM lock operation is issued on PL-4 when SC-1 is active.
• CLM lock operation succeded with following error in syslog.

Apr 22 13:09:01 SYSTEST-CNTLR-1 osafrded[3947]: NO Got peer info request from node 0x2020f with role STANDBY
Apr 22 13:09:01 SYSTEST-CNTLR-1 osafrded[3947]: NO Got peer info response from node 0x2020f with role STANDBY
...
Apr 22 13:09:24 SYSTEST-CNTLR-1 osafclmd[4028]: NO safNode=PL-4,safCluster=myClmCluster LEFT, view number=17
Apr 22 13:09:24 SYSTEST-CNTLR-1 osafclmd[4028]: ER Sending track callback failed
Apr 22 13:09:24 SYSTEST-CNTLR-1 osafclmd[4028]: ER Sending track callback failed
Apr 22 13:09:24 SYSTEST-CNTLR-1 osafclmd[4028]: ER Sending track callback failed
Apr 22 13:09:24 SYSTEST-CNTLR-1 osafclmd[4028]: ER Sending track callback failed
Apr 22 13:09:24 SYSTEST-CNTLR-1 osafclmd[4028]: ER clms_clmresp_ok failed

• Now, if a switchover is invoked and when SC-2 became active, PL-4's admin state is updated as UNLOCKED with out any admin operation on PL-4 CLM object

• At this stage, for every switchover the admin state of payload's CLM object toggles between LOCKED state ( when SC-1 is active ) to UNLOCKED state ( when SC-2 is active).

[Mathi Naickan]

changeset: 7534:f1f6c25f150b
branch: opensaf-5.0.x
parent: 7532:f80647c1a0af
user: Mathi Naickan Mathi.naickan@oracle.com
date: Sun Apr 24 02:10:41 2016 +0530
summary: clm: revert incorrect fix of #1701 - i.e. fix 1738, 1762, 1777

changeset: 7535:546086f9daa2
tag: tip
parent: 7533:fea799faf484
user: Mathi Naickan Mathi.naickan@oracle.com
date: Sun Apr 24 02:10:41 2016 +0530
summary: clm: revert incorrect fix of #1701 - i.e. fix 1738, 1762, 1777

[Mathi Naickan]

The only change related to checkpointing was introduced in the fix of ticket 1701.
So, given that 1738, 1762 is not reproduced if 1701 is removed and given that this ticket also has the same pattern, i have reverted 1701 patch as a fix for the 3 tickets 1738, 1726 and 1777.