Hi Thang,
ack (review + test). In below syslog, I got the assignment of sponsor +
dependent on the locked SC removed, and the other SC creates new active
assignments.
Minor comment: In sg_2n_fsm:node_fail_su_oper(), starting from line
3153, the codes are now most likely the same for both sta
When lock node invokes on active assignment. The dependent SI
follow with sponsor SI move to QUIESCED. There is a case that
the active assignment for sponsor is happening on remain SC node.
And that remaining node was down. The remove SISU only happen for
sponsor SI.
The fix is to remove SUSI of de
When lock node invokes on active assignment. The dependent SI
follow with sponsor SI move to QUIESCED. There is a case that
the active assignment for sponsor is happening on remain SC node.
And that remaining node was down. The remove SISU only happen for
sponsor SI.
The fix is to remove SUSI of de
