Comment 6 for bug 1736102

Ankit,

as Sundar mentioned above, alarms not getting generated for stopped process could be because of
https://bugs.launchpad.net/juniperopenstack/+bug/1742006. The error you are seeing

<BrokerConnection host=10.204.216.105/10.204.216.105 port=9092>: socket disconnected
01/12/2018 05:04:50 AM [kafka.client]: Node 2 connection failed -- refreshing metadata
01/12/2018 05:07:27 AM [kafka.client]: Node 0 connection failed -- refreshing metadata
01/12/2018 05:12:48 AM [kafka.client]: Node 0 connection failed -- refreshing metadata

These are warnings when kafka.client is not able to send a request to kafka, which is essentially a warning and not an error, we do not believe that it is the reason for alarms not getting generated as we were able to generate alarms even when these warnings were there. Could you test a build with #1742006 is fixed and see if you still see that alarms are not generated?

About the warnings, it seems like a library issue and we are investigating it further.