#1753 AMFD re-initializing IMM while stopping OpenSAF services

[Chani Srivastava]

While stopping OpenSAF services on controllers, amfd is seen re-initializing IMM. This is not required.

Setup:
Changeset- 7436
Version - opensaf 5.0

Always reproducible

Apr 13 11:30:22 OSAF-SC2 opensafd: Stopping OpenSAF Services
Apr 13 11:30:22 OSAF-SC2 osafamfnd[2205]: NO Shutdown initiated
Apr 13 11:30:22 OSAF-SC2 osafamfnd[2205]: NO Terminating all AMF components
Apr 13 11:30:22 OSAF-SC2 osafckptd[2221]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osafsmfd[2254]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osafsmfnd[2320]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osafckptnd[2226]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osafevtd[2267]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osafclmna[2116]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osaflckd[2335]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osafntfimcnd[2368]: NO exiting on signal 15
Apr 13 11:30:22 OSAF-SC2 osafimmnd[2155]: NO Implementer disconnected 1578 <290, 2020f> (@OpenSafImmReplicatorB)
Apr 13 11:30:22 OSAF-SC2 osafmsgnd[2270]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osafimmnd[2155]: NO Implementer locally disconnected. Marking it as doomed 1576 <131, 2020f> (MsgQueueService131599)
Apr 13 11:30:22 OSAF-SC2 osafimmnd[2155]: NO Implementer disconnected 1576 <131, 2020f> (MsgQueueService131599)
Apr 13 11:30:22 OSAF-SC2 osaflcknd[2240]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osafrded[2125]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osafmsgd[2305]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osaflogd[2165]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osafimmd[2144]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osafclmd[2185]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osaffmd[2134]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osafimmnd[2155]: exiting for shutdown
Apr 13 11:30:22 OSAF-SC2 osafamfd[2195]: NO Re-initializing with IMM
Apr 13 11:30:22 OSAF-SC2 osafntfd[2175]: exiting for shutdown
Apr 13 11:30:23 OSAF-SC2 osafamfnd[2205]: NO Terminated all AMF components
Apr 13 11:30:23 OSAF-SC2 osafamfnd[2205]: NO Shutdown completed, exiting
Apr 13 11:30:23 OSAF-SC2 app_comp: AL AMF Node Director is down, terminate this process
Apr 13 11:30:23 OSAF-SC2 osafamfd[2195]: exiting for shutdown
Apr 13 11:30:23 OSAF-SC2 kernel: [68307.848209] TIPC: Disabling bearer <eth:eth0>
Apr 13 11:30:23 OSAF-SC2 kernel: [68307.848217] TIPC: Lost link <1.1.2:eth0-1.1.1:eth0> on network plane A
Apr 13 11:30:23 OSAF-SC2 kernel: [68307.848221] TIPC: Lost contact with <1.1.1>
Apr 13 11:30:23 OSAF-SC2 kernel: [68307.848273] TIPC: Left network mode
Apr 13 11:30:23 OSAF-SC2 kernel: [68307.848302] NET: Unregistered protocol family 30
Apr 13 11:30:23 OSAF-SC2 kernel: [68307.848310] TIPC: Deactivated
Apr 13 11:30:23 OSAF-SC2 opensafd: OpenSAF services successfully stopped

[Nagendra Kumar]

The log in question makes not impact on the functionality, so changing the Priority level to Minor.

[Nagendra Kumar]

If Immnd gets killed and Amfd does dispatch, then Amfd gets Bad handle and starts initializing with Imm. This is normal.
But during shutdown case, this may not be desired, but there is no option to tell Amfd that Immnd has exited because of shutdown.
Though this behaviour of Amf doesn;t create any problem to functionality because once Amfnd exists during shutdown, Amfd will also exit and re-initialization happens in a separate thread.

So, I will close it with "wont fix", please comment.