[fuel-qa] master node fails to deploy

Bug #1612571 reported by Alexander Gubanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Critical
Fuel QA Team

Bug Description

Detailed bug description:
Found on CI:
http://cz7776.bud.mirantis.net:8080/jenkins/view/Tempest_9.%D0%A5/job/9.x_Tempest_Ceph_no_ssl/59/console

Steps to reproduce:
   1. Create cluster (FUEL_QA_VER=stable/mitaka)
   2. Deploy cluster

Expected results:
   Fuel node successfuly deployed and passed OSTF

Actual result:
2016-08-11 21:07:05,839 - INFO environment.py:412 -- Waiting for admin node to start up
2016-08-11 21:07:05,841 - INFO environment.py:415 -- Proceed with installation
2016-08-11 21:12:47 - INFO - ssh_client.py:361 -- 10.109.2.2:22> SSHAuth was made from old style creds: SSHAuth for root
2016-08-11 21:12:55,250 - INFO environment.py:412 -- Waiting for admin node to start up
2016-08-11 21:12:55,252 - INFO environment.py:415 -- Proceed with installation
2016-08-11 21:33:04,015 - ERROR __init__.py:67 -- wait_for_provisioning raised: error(113, 'No route to host')
Traceback: Traceback (most recent call last):
  File "/home/jenkins/workspace/9.x_Tempest_Ceph_no_ssl/mos-ci-deployment-scripts/fuel-qa/fuelweb_test/__init__.py", line 60, in wrapped
    result = func(*args, **kwargs)
  File "/home/jenkins/workspace/9.x_Tempest_Ceph_no_ssl/mos-ci-deployment-scripts/fuel-qa/fuelweb_test/models/environment.py", line 478, in wait_for_provisioning
    (self.d_env.admin_net), 22), timeout=timeout)
  File "/home/jenkins/workspace/9.x_Tempest_Ceph_no_ssl/mos-ci-deployment-scripts/fuel-devops-venv/local/lib/python2.7/site-packages/devops/helpers/helpers.py", line 124, in wait_pass
    return raising_predicate()
  File "/home/jenkins/workspace/9.x_Tempest_Ceph_no_ssl/mos-ci-deployment-scripts/fuel-qa/fuelweb_test/models/environment.py", line 478, in <lambda>
    (self.d_env.admin_net), 22), timeout=timeout)
  File "/home/jenkins/workspace/9.x_Tempest_Ceph_no_ssl/mos-ci-deployment-scripts/fuel-devops-venv/local/lib/python2.7/site-packages/devops/helpers/helpers.py", line 65, in tcp_ping_
    s.connect((str(host), int(port)))
  File "/usr/lib/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)
error: [Errno 113] No route to host

Description of the environment:
9.0 GA + snapshot #124

Tags: area-qa
Revision history for this message
Nastya Urlapova (aurlapova) wrote :

@Alex, I would suggest you check your env one more time, because prod BVT is stable for now + SWARM shows perfect results. The last results/sha/versions you can find on prod CI.

Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Alexander Gubanov (ogubanov)
Revision history for this message
Alexander Gubanov (ogubanov) wrote :
Changed in fuel:
assignee: Alexander Gubanov (ogubanov) → Fuel QA Team (fuel-qa)
Changed in fuel:
status: New → Invalid
Revision history for this message
Alexandr Kostrikov (akostrikov-mirantis) wrote :

Error was masked by re-writing exception in fuel-qa code.

The actual cause[0] were with "AssertionError: Ubuntu bootstrap image wasn't built and activated! See logs in /var/log/fuel-bootstrap-image-build.log for details."

[0] https://bugs.launchpad.net/fuel/+bug/1612731

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.