Comment 6 for bug 1716799

Sorry I put it in a wrong way.(contrail-node-mgr not connected to collectors)

What I saw was the same issue as senthil reported in the bug.(ModuleClientState info is not found in the contrail-control-nodemgr generator info) and you mentioned it is because of timing issue.
But I saw after few hours while debugging still ModuleClientState info is not found in the contrail-control-nodemgr generator info and testcase is failing because of that when I reran.

Thanks,
Aswani kumar

If you did not see ModuleClientState then it is same issue, what I mean by timing issue is that the root cause of this is a race between contrail-alarm-gen acquiring a partition and contrail-collector updating the partition but once this issue happens then it will remain in that state until the contrail-control-nodemgr either is restarted or connects to another collector. So then there is no need to open another PR. I will take a look at this. We are also suspecting a librdkafka change that was done recently might be causing this.

Thanks

Megh