Merge remote-tracking branch 'GuidoCasati/dedicated-pcf-config' into integration_2026_w30
ci: split PCF CN config out of shared mini_nonrf_config.yaml (#328) The u0_25prb multi-QoS CI scenario needs PCF (use_local_pcc_rules: no), but in f02c84fc that configuration has been placed in the shared 5g_rfsimulator/mini_nonrf_config.yaml. Every other rfsim pipeline mounts that file without running oai-pcf. In some setups different from Linux (i.e. WSL2) this causes issues. With use_local_pcc_rules: no, SMF attempts associating to oai-pcf when creating SM Context even when no PCF container exists. If that HTTP call exceeds the wait timeout (100 ms), AMF gets error and does not complete the SM context creation, a later Update SM Context then fails ("Could not find Nsmf_PDUSession URI"). Native Linux is usually fine: when the failed PCF association is fast enough, context creation completes successfully. This commit moves PCF-specific configuration into 5g_rfsimulator_u0_25prb only. The shared config is restored to use_local_pcc_rules: yes and a single oai DNN (pre-f02c84fc status). Changes: - Add new file 5g_rfsimulator_u0_25prb/mini_nonrf_config.yaml (PCF, dual-DNN, use_local_pcc_rules: no) and mount in 5g_rfsimulator_u0_25prb/docker-compose.yaml -Revert 5g_rfsimulator/mini_nonrf_config.yaml Reviewed-by:Jaroslava Fiedlerova <jaroslava.fiedlerova@openairinterface.org> Reviewed-by:
Thomas Schlichter <thomas.schlichter@iis.fraunhofer.de>
Showing
Please register or sign in to comment