AMF uses old NSSF address after NSSF IP changed

[gruyaume]

Description

When the NSSF IP addresses changes (ex. after a pod reschedule), the AMF will not use the new address and keep on using the old one resulting in the following error:

2023-11-22T18:50:37.424Z [amf] 2023-11-22T18:50:37Z [ERRO][AMF][GMM][AMF_UE_NGAP_ID:13864935][SUPI:imsi-208930100007487][SUCI:suci-0-208-93-0-0-0-0100007487] Select SMF failed: NSSelection Get Error[NSSF No Response]

The issue seems to be caused by the fact that the AMF only gets the NSSF address from the NRF once when it starts up and keeps on using this address forever. Reference here:

• https://github.com/omec-project/amf/blob/master/consumer/sm_context.go#L96