Test job failed with error: Torrent not found in result

Bug #1594075 reported by Nastya Urlapova
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Low
Fuel DevOps
Mitaka
Invalid
Low
Fuel DevOps
Newton
Invalid
Low
Fuel DevOps

Bug Description

Test jobs were affected by issue with torrent clients:
https://product-ci.infra.mirantis.net/view/9.0_swarm/job/9.0.system_test.ubuntu.unlock_settings_tab/24/console
https://product-ci.infra.mirantis.net/view/9.0_swarm/job/9.0.system_test.ubuntu.plugins.thread_separate_haproxy/12/console
Traceback (most recent call last):
  File "/usr/bin/seedclient.py", line 576, in <module>
    sc.download()
  File "/usr/bin/seedclient.py", line 385, in download
    self._status(torrent)
  File "/usr/bin/seedclient.py", line 40, in f_retry
    return f(*args, **kwargs)
  File "/usr/bin/seedclient.py", line 334, in _status
    t = self.tc.get_torrent(torrent_id=torrent.id)
  File "/usr/lib/python2.7/dist-packages/transmissionrpc/client.py", line 577, in get_torrent
    raise KeyError("Torrent not found in result")
KeyError: 'Torrent not found in result'

I think it was a sporadic issue, but it would be nice find a source of issue just to avoid such failures in future.

Tags: need-info
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

expected result

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
Revision history for this message
Igor Shishkin (teran) wrote :

Unfortunately there is no way at the moment to investigate the issue since job logs are returning 404.
Please let me know if the issue would happen again.

Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

the issue was in incomplete status without any updates, I marked it as invalid.

Please feel free to change status to Confirmed if the issue will be reproduced again.

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.