There is a similar use case that client receive wrong version on MDS_DOWN event. Install server service ver 5 on a vdest then set role to active. Client subscribe server service. Client receive MDS_UP event with ver 5. Change role server service from active to standby then wait await-active timer expired. Client receives MDS_DOWN event with ver always 0.
I think we can leave it once user can use the autoconf 2.7 or later to config it.
amf: dupplicate assignment in roaming SC split brain test
commit 4859bf6a95d336b97d921ea7e7f4c92ecaf85b89 (HEAD -> develop, origin/develop, ticket-3382) Author: Thang Duc Nguyen thang.d.nguyen@endava.com Date: Tue Dec 23 03:02:35 2025 +0100 amf: avoid mismatch in create/delete SUSI object [#3382] This is to correct the previous fix in this ticket. There are some cases that the mismatch can happen. - Create is queued -> delete direct -> create in queue executed. - Delete is queued -> create direct -> delete in queue executed. The fix is based on the mechanism,...
amf: avoid mismatch in create/delete SUSI object [#3382]
amf: dupplicate assignment in roaming SC split brain test
There are some side effects of the fix. It need to be updated.
amf: avoid mismatch in create/delete SUSI object [#3382]