Praveen/Nagu,
I'm seeing an issue where the node admin state is different between
IMM and amfd. I can reproduce this very consistently.
If I power down the standby controller (which is also hosting other
standby SUs), when it comes back up amfd still thinks the admin state is
locked, even though IMM does not. When I am in this state, if I try to
force the admin change, I see:
imm.cc:1756] >> report_admin_op_error: inv:124554051585, res:6, Error
String: 'Clm lock operation going on'
After looking at the code and the traces, it appears that the
ClmResponse to clm_node_exit_start() is never sent.
node->su_cnt_admin_oper is 6 which is correct (the number of the SUs),
so it waits to send the clm response.
I thought maybe we needed to add this to the end of
avd_node_down_mw_susi_failover():
if (avnd->clm_pend_inv != 0) {
// send CLM response
LOG_NO("sending CLM response due to node fail");
saClmResponse_4(cb->clmHandle, avnd->clm_pend_inv,
SA_CLM_CALLBACK_RESPONSE_OK);
avnd->clm_pend_inv = 0;
}
If I add this code, this doesn't totally clear the problem. I
still have to manually unlock the amf node when it comes back up.
How is this supposed to work?
Alex
------------------------------------------------------------------------------
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
