Menu

#3355 amf: saAmfCtDefClcCliTimeout is not updated for non-proxied NPI component

5.25.04
fixed
None
defect
amf
nd
5
minor
False
2025-04-26
2024-06-27
No

Step to reproduce the issue.
- Deploy 2N model with non-proxied NPI component to cluster.
- Unlock-in/Unlock the SU.
- Add sleep time value larger than the saAmfCtDefClcCliTimeout value in SaAmfCompType into termination script.
- Then change the saAmfCtDefClcCliTimeout value lager than the sleep time.
- Lock the SU. The termination script run with error
2024-06-27 14:33:20.842 SC-1 osafamfnd[318]: NO Reason:'Script did not exit within time'

Related

Wiki: ChangeLog-5.25.04

Discussion

  • Thang Duc Nguyen

    • summary: amf: saAmfCtDefClcCliTimeout not update for non-proxied NPI component --> amf: saAmfCtDefClcCliTimeout is not updated for non-proxied NPI component
     
  • Thang Duc Nguyen

    • status: assigned --> review
     
  • Thang Duc Nguyen

    commit 39f81573f1ed7fed69661bdbed188ebcbedaad7d (HEAD -> develop, origin/develop, ticket-3355)
    Author: thang.d.nguyen thang.d.nguyen@dektech.com.au
    Date: Thu Jun 27 18:49:25 2024 +0700

    amf: handle saAmfCtDefClcCliTimeout correctly for non-proxied NPI component [#3355]
    
    Non-proxied NPI component uses the terminate CLC CLI command
    when terminating. Any update to saAmfCtDefClcCliTimeout does
    not take effect.
    The fix is to correct this issue.
    
     
  • Thang Duc Nguyen

    • status: review --> fixed
     
  • Gary Lee

    Gary Lee - 2025-04-26
    • Milestone: 5.25.03 --> 5.25.04
     

Log in to post a comment.

MongoDB Logo MongoDB