RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_user_migrates_directory_to_remote_provider[1oz_2op_deployed]'>>

>   ???

tests/gui/scenarios/test_oneprovider_transfers.py:73: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)

RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_user_migrates_file_to_remote_provider[1oz_2op_deployed]'>>

>   ???

tests/gui/scenarios/test_oneprovider_transfers.py:69: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)

ReadTimeout: HTTPSConnectionPool(host='dev-oneprovider-krakow.default.svc.cluster.local', port=9443): Read timed out. (read timeout=20)
request = <FixtureRequest for <Function 'test_user_replicates_directory_to_remote_provider[1oz_2op_deployed]'>>

    from tests.gui.steps.oneprovider.transfers import *
>   from tests.gui.meta_steps.oneprovider.common import *

tests/gui/scenarios/test_oneprovider_transfers.py:45: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
(200 more lines...)

RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_user_replicates_directory_with_file_on_current_provider_to_the_same_provider[1oz_2op_deployed]'>>

>   ???

tests/gui/scenarios/test_oneprovider_transfers.py:65: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/local/lib/python2.7/dist-packages/pytest_bdd/scenario.py:195: in _execute_scenario
(77 more lines...)

RuntimeError: no "dev-oneprovider-krakow" found in ProvidersPage in Onezone page
request = <FixtureRequest for <Function 'test_user_replicates_file_to_remote_provider[1oz_2op_deployed]'>>

    from tests.gui.steps.oneprovider.metadata import *
>   from tests.gui.steps.oneprovider.shares import *

tests/gui/scenarios/test_oneprovider_transfers.py:41: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
(78 more lines...)

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  3921  100  3921    0     0  12970      0 --:--:-- --:--:-- --:--:-- 12983
Error response from daemon: Cannot kill container ef67177e45cc: Container ef67177e45cc90088d2448e49e435f24ac62389bda036c22881f91c44a420112 is not running
No resources found.
tput: unknown terminal "unknown"
tput: unknown terminal "unknown"
Cloning into 'bamboos'...
Cloning into 'cdmi_swagger'...
Cloning into 'one_env'...
Cloning into 'onepanel_swagger'...
Cloning into 'oneprovider_swagger'...
Cloning into 'onezone_swagger'...
Unable to find image 'onedata/acceptance_gui:v7' locally
v7: Pulling from onedata/acceptance_gui
7b722c1070cd: Already exists
5fbf74db61f1: Already exists
ed41cb72e5c9: Already exists
7ea47a67709e: Already exists
97995cd0f13a: Already exists
10c88a51c005: Already exists
6b2da66c6d06: Already exists
1fd7b61235cd: Already exists
c0f19e67292f: Already exists
f027ecdb209d: Already exists
aae0a881335e: Already exists
a7db47216466: Already exists
6ab88684cedc: Already exists
254a32696681: Already exists
Digest: sha256:1be6b2105d4bf57548733532046bfbca74e9413f928f97a182447171b554898c
Status: Downloaded newer image for onedata/acceptance_gui:v7
Unable to use a TTY - container test-runner did not allocate one
If you don't see a command prompt, try pressing enter.
pod default/test-runner terminated (Error)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  3921  100  3921    0     0   7479      0 --:--:-- --:--:-- --:--:--  7468
Error response from daemon: Cannot kill container a6def5a349d4: Container a6def5a349d4006cd4c95fe7ddd29352c0451e1d6c07f2503a89f071e5f99576 is not running
Error response from daemon: Cannot kill container 24a38370bc90: Container 24a38370bc9057281b76a24c6978e62bab03353ad009dd17ba7f2e241a88431e is not running
Error response from daemon: Cannot kill container ca306cdbd588: Container ca306cdbd588dc2b938d5d36cfe297349e4d4a3f3ffff86ebeb147c13c57454c is not running
Error response from daemon: Cannot kill container 14b4bb584bfb: Container 14b4bb584bfb32242257531a833f9b745f8ec9b3de7bb37b2f1b56cfa91df025 is not running
Error response from daemon: Cannot kill container f266fdb9201b: Container f266fdb9201bfb3055e04eed1ee6cc5021493c7d75595f66343476d4b7fdd063 is not running
Error response from daemon: Cannot kill container b1e2f262686b: Container b1e2f262686b8a3ceb90c795280d9a74fbeca272dbc322367464e336069b8005 is not running
Error response from daemon: Cannot kill container ea5fc3873f7b: Container ea5fc3873f7b853a35f2d0b207183b11f841e2e40105486ac9f55e85a8c86b78 is not running
Error response from daemon: Cannot kill container 31f9e4b857f9: Container 31f9e4b857f9d8460750b44d56ef6f225454e94ace21352695e2ef43862f2c69 is not running
Error response from daemon: Cannot kill container 7f20d194528c: Container 7f20d194528cb51c7139f5b68d5ca20ef8e17740c018253f3a713aa234363a39 is not running
Error response from daemon: Cannot kill container 87b3a6ce87d2: Container 87b3a6ce87d2b40ee1bcb05ee97ba164a4cadf2f086a59698b6801c39743262f is not running
Error response from daemon: Cannot kill container 156ffbe8d887: Container 156ffbe8d88767331cf32d24122eb6669d432c0d2340562db29fb6652661475b is not running
Error response from daemon: Cannot kill container 7767d9b77d62: Container 7767d9b77d62f60495d8be175edf0c6529722698124ccd47f92cc8c0a856b676 is not running
Error response from daemon: Cannot kill container 79bc5e6c1bfd: Container 79bc5e6c1bfdcb486a7e61eb88130636f6f737dba148ca61cfebfa8880c1555a is not running
Error response from daemon: Cannot kill container 9e10652d767c: Container 9e10652d767c613bde9393ab5e49297fa20ed44573c8597e42aa0920c103eb02 is not running
Error response from daemon: Cannot kill container 3f079930b122: Container 3f079930b1228737bbcabd5d88ef2a6d12c47518ab22f61dd9e59ec7403ae67e is not running
Error response from daemon: Cannot kill container e2ce7cdce143: Container e2ce7cdce143ce757c1c1f625ddead2837dfdf254a29ba201953fbc706034343 is not running
Error response from daemon: Cannot kill container ca0fc2b6bbad: Container ca0fc2b6bbad7a21f39c96c337c8b813e661d64e7d509e6bb287f4aa0d7e9c7d is not running
Error response from daemon: Cannot kill container 57fded08ffd1: Container 57fded08ffd15d508919a358a8b5e056c9d53c9560da39440c83145b2071a668 is not running
Error response from daemon: Cannot kill container 3dfcce6106c2: Container 3dfcce6106c2fc468109d8fb35c7fd1aa4be197eabfcc559cb5719fb4592d570 is not running