- **Milestone**: 5.2.FC --> future
---
** [tickets:#2180] mds: Ensure topology events are seen before data messages**
**Status:** assigned
**Milestone:** future
**Created:** Wed Nov 09, 2016 12:07 PM UTC by Anders Widell
**Last Updated:** Fri Nov 11, 2016 08:38 AM UTC
**Owner:** Anders Widell
The problem was seen in AMF after the above mentioned changesets were pushed,
so either it is a different problem or the above changesets do not solve it
properly.
---
** [tickets:#2180] mds: Ensure topology events are seen before data messages**
**Status:** assigned
**Milestone:** 5.2.FC
- **Comment**:
Iam trying to understand the context/scenario of the fix done in the following
changesets
hg log | grep -i "added handling"
summary: MDS: Added handling for out of order of Subscription and Data
messages(2611)
summary: MDS: Added handling for out of order of Subscription
Yes that would be an alternative approach, to let each OpenSAF service handle
this separately. Ticket [#2124] only covers AMF, so we would need to check if
any of the other services are affected (they probably are), and fix them as
well.
---
** [tickets:#2180] mds: Ensure topology events are
This problem is reported in [#2124]
---
** [tickets:#2180] mds: Ensure topology events are seen before data messages**
**Status:** assigned
**Milestone:** 5.2.FC
**Created:** Wed Nov 09, 2016 12:07 PM UTC by Anders Widell
**Last Updated:** Wed Nov 09, 2016 12:07 PM UTC
**Owner:** Anders Widell
---
** [tickets:#2180] mds: Ensure topology events are seen before data messages**
**Status:** assigned
**Milestone:** 5.2.FC
**Created:** Wed Nov 09, 2016 12:07 PM UTC by Anders Widell
**Last Updated:** Wed Nov 09, 2016 12:07 PM UTC
**Owner:** Anders Widell
TIPC does not guarantee that
