Fuel for OpenStack

OSTF test fails with ChannelException: (2, 'Connect failed')

  1. Series mitaka
  2. Bug #1551331
Bug #1551331 reported by Volodymyr Shypyguzov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel QA Team
Fuel for OpenStack 10.0
Mitaka
Confirmed
High
Fuel QA Team
Fuel for OpenStack 9.0
Newton
Invalid
High
Fuel QA Team
Fuel for OpenStack 10.0

Bug Description

Test Launch instance with file injection fails on connection to the created instance
In ostf logs -

fuel_health.nmanager: DEBUG: (2, 'Connect failed'). Another effort needed.
paramiko.transport: DEBUG: EOF in transport thread
fuel_health.common.test_mixins: DEBUG: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/fuel_health/common/test_mixins.py", line 177, in verify
    result = func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/fuel_health/nmanager.py", line 863, in _run_command_from_vm
    ip_address, timeout, retries, cmd, viaHost=viaHost),
  File "/usr/lib/python2.7/site-packages/fuel_health/nmanager.py", line 841, in _run_command_on_instance
    return fuel_health.test.call_until_true(run_cmd, 40, 1)
  File "/usr/lib/python2.7/site-packages/fuel_health/test.py", line 65, in call_until_true
    elif func():
  File "/usr/lib/python2.7/site-packages/fuel_health/nmanager.py", line 837, in run_cmd
    vm=ip_address)
  File "/usr/lib/python2.7/site-packages/fuel_health/nmanager.py", line 437, in retry_command
    self.fail('Execution command on Instance fails '
  File "/usr/lib/python2.7/site-packages/unittest2/case.py", line 666, in fail
    raise self.failureException(msg)
AssertionError: Execution command on Instance fails with unexpected result.

Volodymyr Shypyguzov (vshypyguzov)
Changed in fuel:
assignee: nobody → Fuel QA Team (fuel-qa)
Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

please attach diagnostic snapshot

Changed in fuel:
status: New → Incomplete
milestone: none → 9.0
Revision history for this message
Volodymyr Shypyguzov (vshypyguzov) wrote :
Revision history for this message
Bug Checker Bot (bug-checker) wrote : Autochecker

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

version

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

tags: added: need-info
Oleksiy Molchanov (omolchanov)
Changed in fuel:
status: Incomplete → Confirmed
importance: Undecided → Medium
tags: added: area-qa
Bug Checker Bot (bug-checker)
tags: removed: need-info
Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

Guys test failed according to there is no connectivity to the node- so please re-assign to the correct team
paramiko.transport: ERROR: Secsh channel 0 open FAILED: No route to host: Connect failed
paramiko.transport: DEBUG: EOF in transport thread
fuel_health.nmanager: DEBUG: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/fuel_health/nmanager.py", line 422, in retry_command
    result = method(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/fuel_health/common/ssh.py", line 195, in exec_command_on_vm
    (self.host, 0))
  File "/usr/lib/python2.7/site-packages/paramiko/transport.py", line 740, in open_channel
    raise e
ChannelException: (2, 'Connect failed')

Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Volodymyr Shypyguzov (vshypyguzov)
tags: added: need-info
removed: area-qa
Revision history for this message
Dmitriy Kruglov (dkruglov) wrote :

Occurrence on the latest MOS 9.0 swarm run (ISO build fuel-9.0-mos-368-2016-05-17)
https://product-ci.infra.mirantis.net/job/9.0.system_test.ubuntu.cic_maintenance_mode/113/testReport/(root)/negative_auto_cic_maintenance_mode/negative_auto_cic_maintenance_mode/

Revision history for this message
Dmitriy Kruglov (dkruglov) wrote :
Sergey Shevorakov (sshevorakov)
tags: added: swarm-fail
Revision history for this message
Sergey Shevorakov (sshevorakov) wrote :

Raised priority to High, since it fails 1 Swarm TC.

Revision history for this message
Ksenia Svechnikova (kdemina) wrote :

@Sergey
When you add swarm-fail tag and raise priority, please add any information about what TC is failed by this issue. As for now it's not clear what Milestone it affects and at what test should we look.

Revision history for this message
Sergey Shevorakov (sshevorakov) wrote :

Here is the case: https://mirantis.testrail.com/index.php?/tests/view/6590094

Revision history for this message
Sergey Shevorakov (sshevorakov) wrote :

I was talking about 9.0, since the bug appeared in 9.0 ISO #423 Swarm results.
https://mirantis.testrail.com/index.php?/plans/view/12298

Revision history for this message
Ksenia Svechnikova (kdemina) wrote :

Reassign 9.0 for vshypyguzov, same as it's in 10.0

In case if it's not qa issue, please reassign to the proper team

Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :

As it was stated there is no connectivity to the node so it's not qa issue

Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

Guys, please don't drop bugs. It is either issue with QA test or with CI configuration or with deployment or with OSTF test. Please find a root cause and move to the proper team.

Revision history for this message
Volodymyr Shypyguzov (vshypyguzov) wrote :

Moving to Invalid since it wasn't reproduced for a long time

Revision history for this message
Timofey Durakov (tdurakov) wrote :

the issue is reproduced again, there are little details on the snapshot logs:
https://ci.fuel-infra.org/job/10.0-community.main.ubuntu.bvt_2/1251/console

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

Other bug subscribers

Remote bug watches

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