fix: release twice uecontext when handover #143
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andy89923
approved these changes
Sep 17, 2024
|
Hi @ss920386 Thanks! |
ss920386
reviewed
Sep 18, 2024
ss920386
approved these changes
Sep 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In free5GC v3.4.3, during an N2 handover, two "release UE context" messages are sent, causing an error during the second "handle release UE context complete."
Before the fix, when running ./test.sh TestN2Handover, the result is as shown in the picture.
The system sends the "release UE context" twice, but since the test function only handles it once, no error occurs.
After the fix, when running ./test.sh TestN2Handover, the result is as shown in the picture, and only one "release UE context" is sent.
Related Issues
free5gc/free5gc#604