Assertion fails on arrival of optional F1AP message GNB-DU CONFIGURATION UPDATE
If a message of type GNB-DU CONFIGURATION UPDATE is sent to the OAI O-CU it fails with an assertion inside the function f1ap_decode_initiating_message()
here:
https://gitlab.eurecom.fr/oai/openairinterface5g/-/blob/develop/openair2/F1AP/f1ap_decoder.c#L106
Assertion (0) failed!
In f1ap_decode_initiating_message() ../../../openair2/F1AP/f1ap_decoder.c:106
Unknown procedure ID (3) for initiating message
It appears that OAI does not have a F1AP handler for the (optional) GNB-DU CONFIGURATION UPDATE message as of now.
It is not a critical issue as the same information can already be included in the F1 SETUP REQUEST but it can be a problem that the application exits when receiving the message type. E.g. the O-RAN SC O-DU-L2 always sends the GNB-DU CONFIGURATION UPDATE F1AP message and expects a reply (the code is not flexible at all, but that's a different issue).