- **status**: review --> fixed
- **Comment**:
commit 8ec9b8dbac32390ffb7b97833842007bc6aaef6f (HEAD -> develop,
origin/develop, ticket-3396)
Author: Thien Minh Huynh <[email protected]>
Date: Thu Apr 9 11:30:52 2026 +0700
mds: fix MxN standby on service operation down [#3396]
commit 544764998d9ec61060e8dd1f5a81f2e8bdb7c690
Author: Thien Minh Huynh <[email protected]>
Date: Thu Apr 9 10:06:41 2026 +0700
mds: add test case for verify replacement active [#3396]
commit c99a9e0a8a1bb4c89f5c8af3504558934093f9bc
Author: Thien Minh Huynh <[email protected]>
Date: Thu Apr 9 10:06:31 2026 +0700
mds: fix replacement active callback metadata [#3396]
---
**[tickets:#3396] MDS: NEW\_ACTIVE metadata is incorrect after MxN VDEST
active-to-standby transition**
**Status:** fixed
**Milestone:** 5.27.01
**Created:** Mon Apr 13, 2026 08:08 AM UTC by Thien Minh Huynh
**Last Updated:** Wed Apr 22, 2026 09:44 AM UTC
**Owner:** Thien Minh Huynh
Steps to reproduce
------------------
1. Start MDS in two separate processes.
2. In the first process, create MxN VDEST 1001 and install service 600 with
private version 1.
3. Change VDEST 1001 to ACTIVE in the first process.
4. In the subscriber process, install service 500 and subscribe to service 600
with INTRACHASSIS scope.
5. Verify that subscriber 500 receives an initial UP event for service 600 with
private version 1.
6. In the second process, create the same MxN VDEST 1001 and install a
replacement instance of service 600 with private version 2.
7. Promote the second process VDEST 1001 to ACTIVE and demote the first process
VDEST 1001 to STANDBY.
8. Retrieve subscription events on service 500 after the role transition.
Observed behaviour
------------------
After the ACTIVE to STANDBY handover on MxN VDEST 1001, the subscriber does
receive the expected sequence of service-change notifications, including
NO_ACTIVE followed by NEW_ACTIVE. However, the payload associated with the
NEW_ACTIVE notification is
not preserved from the replacement active instance.
Expected behaviour
------------------
When the original ACTIVE instance of service 600 is demoted to STANDBY and the
replacement instance becomes ACTIVE on the same MxN VDEST, the subscriber
should receive:
1. a NO_ACTIVE event reflecting the demoted instance, then
2. a NEW_ACTIVE event reflecting the replacement instance.
The NEW_ACTIVE metadata must report the replacement service attributes,
specifically:
- role = ACTIVE
- private version = 2
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list._______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
