Comment 2 for bug 1610745

We checked the configuration and both vrouter (nodeg17 and nodec38) agents are correctly connected to 2 of the 3 control nodes. Please see below:

http://nodeg21.englab.juniper.net:5998/clients

There seems to be a problem in the test case. Can someone look into this from test team? The analysis of failure may not be correct.

Logs are showing :

2016-08-08 17:40:15,501 - DEBUG - Requesting: http://10.204.217.176:8081/analytics/uves/generator/nodec38:Compute:contrail-vrouter-agent:0?flat
2016-08-08 17:40:15,524 - DEBUG - Requesting: http://10.204.217.176:8081/analytics/uves/vrouter/nodec38?flat
2016-08-08 17:40:15,548 - ERROR - vrouter nodec38 not connected to 2 xmpp peers, should connect to at least one more from set(['10.204.217.61'])
2016-08-08 17:40:18,551 - DEBUG - Requesting: http://10.204.217.176:8081/analytics/uves/generator/nodec38:Compute:contrail-vrouter-agent:0?flat
2016-08-08 17:40:18,567 - DEBUG - Requesting: http://10.204.217.176:8081/analytics/uves/vrouter/nodec38?flat
2016-08-08 17:40:18,592 - ERROR - vrouter nodec38 not connected to 2 xmpp peers, should connect to at least one more from set(['10.204.217.61'])

Test seems to look for connection from agent to node 10.204.217.61, but it is already connected to 10.204.217.73 and 10.204.217.98).