The problem seems to be that a topology event is arriving after the data event:
<139>1 2017-06-01T00:32:21.356449+02:00 SC-1 osafimmd 207 mds.log [meta
sequenceId="79"] MDS_SND_RCV:No Route Found from svc_id = IMMD(24), to svc_id =
IMMND(25) on Adest = <0x0002020f, 665691278>
<139>1
- **status**: accepted --> unassigned
- **assigned_to**: Praveen --> nobody
---
** [tickets:#2485] amfnd: missing susi response if component is restarted**
**Status:** unassigned
**Milestone:** 5.17.06
**Created:** Wed Jun 07, 2017 12:57 AM UTC by Gary Lee
**Last Updated:** Fri Jun 09, 2017
---
** [tickets:#2491] imm: PBE regenerates imm.db if immnd exits during the PBE
state verification**
**Status:** accepted
**Milestone:** 5.17.06
**Created:** Fri Jun 09, 2017 09:18 AM UTC by Zoran Milinkovic
**Last Updated:** Fri Jun 09, 2017 09:18 AM UTC
**Owner:** Zoran Milinkovic
If
Attached is the configuration to reproduce the issue.
Steps to reproduce:
1)Bring SC-1 with attached imm.xml
2)After cluster time expiry, AMF will start two NPI components as part of
assignment.
3) Make some delay between instantiation of two NPI components script.
4) Restart the already
- **status**: accepted --> review
---
** [tickets:#2487] imm: IMMND crashes in immnd_proc_discard_other_nodes**
**Status:** review
**Milestone:** 5.17.06
**Created:** Wed Jun 07, 2017 10:58 AM UTC by Hung Nguyen
**Last Updated:** Wed Jun 07, 2017 10:58 AM UTC
**Owner:** Hung Nguyen
