Hi Wang, The ip should be correct. It's possible that the ip in the log message is slightly different because it refers to a different instance floating ip?
If you have a nodepool image uploaded already, I suggest you try to manually launch a node using that image outside of nodepool. You should be able to ssh into it as Ubuntu user using the ssh private key provided when you created the image. Ramy -----Original Message----- From: Wang Shilong [mailto:wshil...@ddn.com] Sent: Wednesday, February 08, 2017 6:26 AM To: openstack-infra@lists.openstack.org Cc: Li Xi <l...@ddn.com> Subject: Re: [OpenStack-Infra] About setting up CI Hello Guys, I am following https://github.com/openstack-infra/puppet-openstackci/blob/master/doc/source/third_party_ci.rst to setup CI. I hit following problem from nodepool log. 2017-02-08 22:59:35,529 ERROR nodepool.utils: Exception while testing ssh access to 172.24.4.2: Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/nodepool/nodeutils.py", line 55, in ssh_connect client = SSHClient(ip, username, **connect_kwargs) File "/usr/local/lib/python2.7/dist-packages/nodepool/sshclient.py", line 32, in __init__ allow_agent=allow_agent) File "/usr/local/lib/python2.7/dist-packages/paramiko/client.py", line 305, in connect retry_on_signal(lambda: sock.connect(addr)) File "/usr/local/lib/python2.7/dist-packages/paramiko/util.py", line 270, in retry_on_signal return function() File "/usr/local/lib/python2.7/dist-packages/paramiko/client.py", line 305, in <lambda> retry_on_signal(lambda: sock.connect(addr)) File "/usr/lib/python2.7/socket.py", line 224, in meth return getattr(self._sock,name)(*args) error: [Errno 110] Connection timed out 2017-02-08 22:59:37,533 ERROR nodepool.NodeLauncher: Timeout launching node id: 4311 in provider: local_01 error: Timeout waiting for ssh access After some checking, problem is openstack VM instance ip is not what openstack specified, for example for above case, indeed allocation ip of VM is 172.24.4.5. So nodepool always failed because of this reasons, how can i slove this mismatch problems and proceed CI testing? Thank you! Shilong ________________________________________ From: Wang Shilong Sent: Thursday, November 17, 2016 21:21 To: openstack-infra@lists.openstack.org Cc: Li Xi Subject: About setting up CI Hello folks, We are trying to setting up CI testing system for new Lustre cinder Drivers. I try to do as following URL In centos7: http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/ But hit the following problem: [root@vm7-1 ~]# ./install_master.sh Using upstream Gerrit user: ddn_openstack Using Jenkins SSH key path: /root/data/jenkins_key Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Error: Could not find template 'openstack_project/puppet.conf.erb' at /root/os-ext-testing/puppet/modules/os_ext_testing/manifests/base.pp:132 on node vm7-1 Error: Could not find template 'openstack_project/puppet.conf.erb' at /root/os-ext-testing/puppet/modules/os_ext_testing/manifests/base.pp:132 on node vm7-1 I guess this Doc might be out of date, could you please give me some hints how I can setup latest CI? Thanks for your suggestion! Shilong _______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra _______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
