Tempest test_server_connectivity_reboot is failed

Bug #1566270 reported by Sergii Turivnyi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Status tracked in 10.0.x
10.0.x
Confirmed
High
MOS Nova

Bug Description

Detailed bug description:
ISO: http://paste.openstack.org/show/492962/
Configuration: [9.0][MOSQA] Tempest 9.0 (VLAN_CINDER-TEMPEST,HA,Cinder LVM,Swift(api))

Steps to reproduce:
Deploy ISO in configuration see (Detailed bug description)

Expected results:
Test is passed

Actual result:
Test is Failed

Reproducibility:
See attachment

Workaround:
---

Impact:
---

Description of the environment:
See (Detailed bug description)

Additional information:
Error Message

test failed

Stacktrace

Traceback (most recent call last):
  File "tempest/test.py", line 113, in wrapper
    return f(self, *func_args, **func_kwargs)
  File "tempest/scenario/test_network_advanced_server_ops.py", line 115, in test_server_connectivity_reboot
    server, keypair, floating_ip)
  File "tempest/scenario/test_network_advanced_server_ops.py", line 93, in _wait_server_status_and_check_network_connectivity
    self._check_network_connectivity(server, keypair, floating_ip)
  File "tempest/scenario/test_network_advanced_server_ops.py", line 86, in _check_network_connectivity
    servers=[server])
  File "tempest/scenario/manager.py", line 599, in check_public_network_connectivity
    should_connect=should_connect)
  File "tempest/scenario/manager.py", line 583, in check_vm_connectivity
    msg=msg)
  File "/home/rally/.rally/tempest/for-deployment-4755604f-fa48-483a-996f-1633957cf9ed/.venv/local/lib/python2.7/site-packages/unittest2/case.py", line 702, in assertTrue
    raise self.failureException(msg)
AssertionError: False is not true : Timed out waiting for 10.109.4.139 to become reachable

Revision history for this message
Sergii Turivnyi (sturivnyi) wrote :
Changed in mos:
status: New → Confirmed
tags: added: nova
Changed in mos:
assignee: Oleksiy Butenko (obutenko) → nobody
Dina Belova (dbelova)
tags: added: area-nova
removed: nova
Revision history for this message
Dina Belova (dbelova) wrote :

MOS Nova team, please take a look. VM was not reached after the timeout passed.

Changed in mos:
assignee: nobody → MOS Nova (mos-nova)
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

Sergii, my current understanding is that this is a duplicate of https://bugs.launchpad.net/mos/+bug/1571704 , please re-open the bug, if this is still reproduced, when the former is fixed.

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.