Comment 1 for bug 1454980

Revision history for this message
Ignatious Johnson Christopher (ijohnson-x) wrote : Re: fab depends on connection to internal vIP for provisioning

From below logs the Fab have connected to [root@172.16.70.10] -- External network and executing "local: python /opt/contrail/utils/provision_vrouter.py" locally in node [root@172.16.70.10].

logs:
---------
 2015-05-14 00:24:28:853736: [root@172.16.70.10] out: [localhost] local: python /opt/contrail/utils/provision_vrouter.py --host_name csol1-node10 --host_ip 172.16.80.10 --api_server_ip 172.16.80.25 --oper add --admin_user admin --admin_password c0ntrail123 --admin_tenant_name admin --openstack_ip 172.16.80.25

provision_vrouter.py will connect to api server thought internal network(--api_server_ip 172.16.80.25) and add the vrouter node to the config. Looks like connection from compute node(root@172.16.70.10) to api-server is not established from the below logs,

logs:
---------
2015-05-14 00:24:31:982209: [root@172.16.70.10] out: File "/usr/lib/python2.7/dist-packages/vnc_api/vnc_api.py", line 391, in _request
2015-05-14 00:24:31:982753: [root@172.16.70.10] out: raise ConnectionError
2015-05-14 00:24:31:983288: [root@172.16.70.10] out: requests.exceptions.ConnectionError