In current implementation, ntfsv does not deal with SA_AIS_ERR_TRY_AGAIN
when calling saClmInitialize
. If that is the case, ntfsv will be exited, and in consequence, the node will be reboot.
Below is the trace log, happened when testing roaming SC:
2016-11-15 18:13:25 SC-3 osafntfd[458]: ER saClmInitialize failed with error: 6
2016-11-15 18:13:25 SC-3 osafrded[412]: NO Peer down on node 0x2020f
Tickets: #2191
Tickets: #2192
Wiki: ChangeLog-5.0.2
Wiki: ChangeLog-5.1.1
changeset: 8357:2f1901bd5e3f
tag: tip
parent: 8354:288991466a47
user: Vu Minh Nguyen vu.m.nguyen@dektech.com.au
date: Thu Nov 17 13:10:24 2016 +0700
summary: ntf: handle error code TRY_AGAIN of saClmInitialize() [#2191]
changeset: 8356:898ed6baeb2f
branch: opensaf-5.1.x
parent: 8352:15416dce3e2d
user: Vu Minh Nguyen vu.m.nguyen@dektech.com.au
date: Thu Nov 17 13:10:24 2016 +0700
summary: ntf: handle error code TRY_AGAIN of saClmInitialize() [#2191]
changeset: 8355:6833e9b1d421
branch: opensaf-5.0.x
parent: 8351:4eb1ebe62d35
user: Vu Minh Nguyen vu.m.nguyen@dektech.com.au
date: Thu Nov 17 13:10:24 2016 +0700
summary: ntf: handle error code TRY_AGAIN of saClmInitialize() [#2191]
Related
Tickets:
#2191