XMPP connection failure for compute nodes

[Sudheendra Rao]

XMPP connection failures for compute nodes on build68 of R2.0
The problem is seen on both centos and ubuntu.

root@nodec60:~#
root@nodec60:~# contrail-status
== Contrail vRouter ==
supervisor-vrouter: active
contrail-vrouter-agent initializing (Collector, Discovery:Collector, Discovery:dns-server, Discovery:xmpp-server connection down)
contrail-vrouter-nodemgr active

root@nodec60:~#

This is a multi-interface setup and able to ping control-data interface of config from all the compute nodes in the cluster:

root@nodec60:~# ifconfig vhost0
vhost0 Link encap:Ethernet HWaddr 00:25:90:c4:98:b3
          inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0
          inet6 addr: fe80::225:90ff:fec4:98b3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:278135 errors:0 dropped:0 overruns:0 frame:0
          TX packets:284282 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4210029423 (4.2 GB) TX bytes:32639501 (32.6 MB)

root@nodec60:~#

root@nodec60:~# ping 192.168.10.4
PING 192.168.10.4 (192.168.10.4) 56(84) bytes of data.
64 bytes from 192.168.10.4: icmp_req=1 ttl=64 time=0.125 ms
64 bytes from 192.168.10.4: icmp_req=2 ttl=64 time=0.134 ms

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/14504
Submitter: Nipa Kumar (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/14504
Committed: http://github.org/Juniper/contrail-controller/commit/7ef7f9bdfa0ff380e4445b0a4dbde1c0ff1f142b
Submitter: Zuul
Branch: R2.0

commit 7ef7f9bdfa0ff380e4445b0a4dbde1c0ff1f142b
Author: Nipa Kumar <email address hidden>
Date: Sat Oct 17 11:06:54 2015 -0700

Max control nodes limited to 2.

Set default number of control-nodes to 2 both during config file parsing
and command line argument parsing.
For R2.0 infrastructure does not support setting default discovery-server,
even though the config had discovery-server ip, it was always set to default
and hence agent could never contact the right DiscoveryServer to get
connection information.

Change-Id: Ibb4ca7461e3ef6da937901bac3334902ed7af9c6
Closes-Bug:1507028