SMF sometimes takes wrong values of up_function_features
It looks like it is a race condition. It happens when SMF is sending two PFCP association requests because of a timeout and UPF answers then both of them.
in that case, the up_function_features are wrong and e.g. in smf_procedure
, the FTUP value is set to 0, although signaling-wise it is 1.
cn5g_fed_tutorials_logs_failed_ci_run.zip
Note: The issue in SMF that the generated F-TEID has 0.0.0.0
IP address is fixed, but this is just an aftereffect
Edited by Stefan Spettel