Some network-related test is using wait_for/TimeoutException incorrectly, providing objects that are not compatible with expected by TimeoutException,
which produces the following log:
Traceback (most recent call last):
File "/opt/stack/.venv/lib/python2.7/site-packages/rally/benchmark/runners/base.py", line 79, in _run_scenario_once
method_name)(**kwargs) or scenario_output
File "/opt/stack/.venv/lib/python2.7/site-packages/rally/benchmark/scenarios/vm/vmtasks.py", line 85, in boot_runcommand_delete
**kwargs)
File "/opt/stack/.venv/lib/python2.7/site-packages/rally/benchmark/scenarios/vm/utils.py", line 93, in _boot_server_with_fip
self._wait_for_ping(fip["ip"])
File "/opt/stack/.venv/lib/python2.7/site-packages/rally/benchmark/scenarios/base.py", line 261, in func_atomic_actions
f = func(self, *args, **kwargs)
File "/opt/stack/.venv/lib/python2.7/site-packages/rally/benchmark/scenarios/vm/utils.py", line 134, in _wait_for_ping
timeout=120
File "/opt/stack/.venv/lib/python2.7/site-packages/rally/benchmark/utils.py", line 121, in wait_for
resource_status=get_status(resource))
TimeoutException: Rally tired waiting for unicode u'172.16.44.181':<no id> to become <function _ping_ip_address at 0x7feea65c3488> current status NONE
You can find Diagnostic Snapshot for this case here: http:// mos-scale- share.mirantis. com/fuel- snapshot- 2015-05- 12_15-01- 52.tar. xz