IndexError: list index out of range
request = <FixtureRequest for <Function 'test_user_fails_to_recall_archive_if_there_is_no_space_enough_on_device[1oz_1op_deployed]'>>

    @pytest.mark.usefixtures(*function_args)
    def scenario_wrapper(request):
>       _execute_scenario(feature, scenario, request, encoding)

/usr/local/lib/python3.6/dist-packages/pytest_bdd/scenario.py:227: 
(28 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  47969      0 --:--:-- --:--:-- --:--:-- 47479
Error response from daemon: Cannot kill container: 13248645754c: Container 13248645754cf4559f5bc9dedc53b77a2a825d4a408f9006fc97e88ec9bdf42d is not running
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'bamboos'
Submodule 'cdmi_swagger' (ssh://git@git.onedata.org:7999/vfs/cdmi-swagger.git) registered for path 'cdmi_swagger'
Submodule 'one_env' (ssh://git@git.onedata.org:7999/vfs/one-env.git) registered for path 'one_env'
Submodule 'onepanel_swagger' (ssh://git@git.onedata.org:7999/vfs/onepanel-swagger.git) registered for path 'onepanel_swagger'
Submodule 'oneprovider_swagger' (ssh://git@git.onedata.org:7999/vfs/oneprovider-swagger.git) registered for path 'oneprovider_swagger'
Submodule 'onezone_swagger' (ssh://git@git.onedata.org:7999/vfs/onezone-swagger.git) registered for path 'onezone_swagger'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/onezone_swagger'...
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'onepanel_swagger/bamboos'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/onepanel_swagger/bamboos'...
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'oneprovider_swagger/bamboos'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/oneprovider_swagger/bamboos'...
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'onezone_swagger/bamboos'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error: could not find tiller
Error: could not find tiller
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
W0412 06:29:33.771331     713 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
cp: cannot stat 'onedata/one_env/sources_info.yaml': No such file or directory
  % 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  4653  100  4653    0     0  34723      0 --:--:-- --:--:-- --:--:-- 34723
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: e0de9d531861: Container e0de9d53186123f010b9ffa71cfff3d20092136fa5367fcd521ec38aa219f648 is not running
Error response from daemon: Cannot kill container: 966ea3a20125: Container 966ea3a201254bb8348a9df2980cd5a16d3abaffcd612128e1e8006a7360283a is not running
Error response from daemon: Cannot kill container: f969a2d51a1e: Container f969a2d51a1ee729bff01bfb6939338e866b081c24967945d18e21f5fa339f90 is not running
Error response from daemon: Cannot kill container: c20aac151fa5: Container c20aac151fa50c09805d2fd3ebd430a3a7508e0f1d0fea153ab77416f6d58f83 is not running
Error response from daemon: Cannot kill container: 5bdace571128: Container 5bdace5711283ac6d21c7924d86ac7c0af3251a19c97e593ae11075e61d68613 is not running
Error response from daemon: Cannot kill container: 5b6c3b31050c: Container 5b6c3b31050c4cba022963d3b6f98853efae1beb598d67abad1fdd9aaf5d1e78 is not running
Error response from daemon: Cannot kill container: 9caa19297ff2: Container 9caa19297ff2d886d4a736246c42ed8883c2f06ec119d01f20203d6f5c081039 is not running
Error response from daemon: Cannot kill container: 3998fbfea524: Container 3998fbfea5241ed083dfb4ad6ff05959a95f0394765526f92fd294d65af4d377 is not running
Error response from daemon: Cannot kill container: a8c04663f19f: Container a8c04663f19fb5ad42ff21cdb384d4e73a4781ceb211bc5f49e4ac92c9989ceb is not running
Error response from daemon: Cannot kill container: 9bec56a541da: Container 9bec56a541daee0aa40d5fd1c52820a9ed2da0be2889de2dc080fc19107ccc63 is not running
Error response from daemon: Cannot kill container: 3e6cd83bff43: Container 3e6cd83bff43b57921205b691245061c4719eb8a9da81c16174037ff2563ebb5 is not running
Error response from daemon: Cannot kill container: 90b07babad41: Container 90b07babad41ee74e152d48a99769c04c19331951f036a81cb9443c12a16767e is not running
Error response from daemon: Cannot kill container: 7d71fb0330ac: Container 7d71fb0330ac9c384715bbf9c71dd3420b759fd352af1b201dcfcf1ec1e31a38 is not running
Error response from daemon: Cannot kill container: 86138c0cc662: Container 86138c0cc66291c8b5584de12a1dc341531ee8b975e0a4d90eafbdd30aa08ea2 is not running
Error response from daemon: Cannot kill container: 3e0e437ae23e: Container 3e0e437ae23edc68c7661da0d984f1dc0eae6163e03c0938c2f5dc96497e0c4c is not running
Error response from daemon: Cannot kill container: f9abe52ccb7e: Container f9abe52ccb7ea4c68e823355427e687922dc548dfbc7160ce72eb2860cbf23ea is not running