[system-tests]Index error in l3 failover tests

Bug #1435926 reported by Tatyanka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Incomplete
Medium
Fuel QA Team

Bug Description

http://jenkins-product.srt.mirantis.net:8080/job/6.1.system_test.centos.ha_neutron_destructive/71/testReport/%28root%29/neutron_l3_migration_after_destroy/neutron_l3_migration_after_destroy/?

Error Message

list index out of range

Stacktrace

Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  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/6.1.system_test.centos.ha_neutron_destructive/fuelweb_test/helpers/decorators.py", line 66, in wrapper
    return func(*args, **kwargs)
  File "/home/jenkins/workspace/6.1.system_test.centos.ha_neutron_destructive/fuelweb_test/tests/tests_strength/test_neutron.py", line 282, in neutron_l3_migration_after_destroy
    devops_node = self.get_node_with_dhcp(self, os_conn, net_id)
  File "/home/jenkins/workspace/6.1.system_test.centos.ha_neutron_destructive/fuelweb_test/tests/tests_strength/test_neutron.py", line 34, in get_node_with_dhcp
    node = os_conn.get_node_with_dhcp_for_network(net_id)[0]
IndexError: list index out of range

Tags: system-tests
Changed in fuel:
status: New → Confirmed
summary: - Index error in l3 failover tests
+ [system-tests]Index error in l3 failover tests
Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :

I didn't observe this issue yesterday, but I think we should simply add some check in case we get empty list to avoid it. So it can be moved to 7.0 with medium priority

Changed in fuel:
importance: High → Medium
milestone: 6.1 → 7.0
status: Confirmed → Incomplete
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.