Deploy amf demo on the cluster. Stop opensafd service via systemctl. Log printed in syslog
2026-06-16 01:49:27.997 SC-1 systemd[1]: Stopping OpenSAF daemon...
2026-06-16 01:49:28.014 SC-1 opensafd: Stopping OpenSAF Services
2026-06-16 01:49:28.016 SC-1 osafamfnd[287]: NO Shutdown initiated
2026-06-16 01:49:28.016 SC-1 osafamfnd[287]: NO Removing assignments from AMF components
2026-06-16 01:49:28.016 SC-1 amf_demo[520]: CSI Remove for 'safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1'
2026-06-16 01:49:28.016 SC-1 osafamfnd[287]: NO Removed 'safSi=AmfDemo,safApp=AmfDemo1' from 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
2026-06-16 01:49:28.016 SC-1 osafamfnd[287]: NO Removed assignments from AMF components
2026-06-16 01:49:28.016 SC-1 osafamfnd[287]: NO Terminating all AMF components
...
Only have 'Removed' SI. It should add a 'Removing' record as a pair, used for troubleshooting.
Attached patch for reference.
Fix duplicate message when trying to lock the SU. Message looked like
I updated the fix patch resolving the duplicate issue.
Below: logging output after fixing the 2 unexpected logging:
But I need to dig into more NPI removal workflows, there could be above logging situations not yet covered
After running many tests, I found that NPI with 1 SI logs nothing even with the current fix patch applied.
Unfortunately, None of the resources support NPI with multiple SI.
In V1 version, keep the below code due to it is not modified.
commit 55de4942aa5786801ef0b3c1ed078cdb5fb1dbd0 (HEAD -> develop, origin/develop, ticket-3400)
Author: Nguyen Tran Trung Hau Hau.Nguyen@endava.com
Date: Mon Jun 22 10:31:09 2026 +0000