Ironic tests failed with timeout on step verification connectivity by ssh for created VM on ironic node

Bug #1539565 reported by Tatyanka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
New
High
MOS Ironic
8.0.x
New
High
MOS Ironic

Bug Description

Both tests for ironic (swift/ceph https://product-ci.infra.mirantis.net/job/8.0.system_test.ubuntu.ironic_deploy_swift/4/console) failed with
ERROR: Deploy ironic with 1 baremetal node
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jenkins/venv-nailgun-tests-2.9/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/home/jenkins/venv-nailgun-tests-2.9/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/home/jenkins/venv-nailgun-tests-2.9/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/8.0.system_test.ubuntu.ironic_deploy_swift/fuelweb_test/helpers/decorators.py", line 83, in wrapper
    result = func(*args, **kwargs)
  File "/home/jenkins/workspace/8.0.system_test.ubuntu.ironic_deploy_swift/fuelweb_test/tests/test_ironic_base.py", line 194, in ironic_deploy_swift
    ironic_conn.verify_vms_connection(ironic_conn)
  File "/home/jenkins/workspace/8.0.system_test.ubuntu.ironic_deploy_swift/fuelweb_test/helpers/ironic_actions.py", line 101, in verify_vms_connection
    timeout=60 * 5, timeout_msg='Failed to connect to port 22')
  File "/home/jenkins/venv-nailgun-tests-2.9/local/lib/python2.7/site-packages/devops/helpers/helpers.py", line 94, in wait
    raise TimeoutError(timeout_msg)
TimeoutError: Failed to connect to port 22

After revert of environment I can ping instance, telnet to it by 22 port, so looks like we need to fix test here:

[root@nailgun ~]# fuel node
id | status | name | cluster | ip | mac | roles | pending_roles | online | group_id
---|--------|----------------------------|---------|-------------|-------------------|--------------------|---------------|--------|---------
2 | ready | slave-02_controller_ironic | 1 | 10.109.16.4 | 64:49:ae:ff:55:2e | controller, ironic | | True | 1
3 | ready | slave-03_controller_ironic | 1 | 10.109.16.5 | 64:3e:4a:17:4a:e6 | controller, ironic | | True | 1
5 | ready | slave-01_controller | 1 | 10.109.16.3 | 64:7f:27:39:00:e4 | controller | | True | 1
1 | ready | slave-05_compute | 1 | 10.109.16.7 | 64:3d:36:66:b3:38 | compute | | True | 1
4 | ready | slave-04_ironic | 1 | 10.109.16.6 | 64:71:00:60:43:ef | ironic | | True | 1
[root@nailgun ~]# ssh node-5
Warning: Permanently added 'node-5' (ECDSA) to the list of known hosts.
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-76-generic x86_64)

 * Documentation: https://help.ubuntu.com/
root@node-5:~# . openrc
root@node-5:~# nova list
+--------------------------------------+-----------------+--------+------------+-------------+-------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-----------------+--------+------------+-------------+-------------------------+
| 052ddbba-b025-470f-b1db-781b45127b38 | ironic-slave-01 | ACTIVE | - | Running | baremetal=10.109.19.131 |
+--------------------------------------+-----------------+--------+------------+-------------+-------------------------+

root@node-4:~# ping 10.109.19.131
PING 10.109.19.131 (10.109.19.131) 56(84) bytes of data.
64 bytes from 10.109.19.131: icmp_seq=1 ttl=64 time=0.745 ms
64 bytes from 10.109.19.131: icmp_seq=2 ttl=64 time=0.841 ms
64 bytes from 10.109.19.131: icmp_seq=3 ttl=64 time=0.317 ms
^C
--- 10.109.19.131 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms

root@node-4:~# telnet 10.109.19.131 22
Trying 10.109.19.131...
Connected to 10.109.19.131.
Escape character is '^]'.
SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.4

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.