RuntimeError: file file1(1) has not been downloaded
request = <FixtureRequest for <Function 'test_user_downloads_symlink_of_file[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: 
(34 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  4653  100  4653    0     0  37224      0 --:--:-- --:--:-- --:--:-- 37224
Error response from daemon: Cannot kill container: 89d54710a072: Container 89d54710a072c284114f5a53c7511250b8bea478076b5decfea11d3be3536e1a 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-COSL/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/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-COSL/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-COSL/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-COSL/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: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
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]
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
W0630 08:49:12.367044     444 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  39769      0 --:--:-- --:--:-- --:--:-- 39769
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 422f002ce079: Container 422f002ce0793d65a88d5f6a4916aa2de9e669b86c3e67fd4aec52be5b51523d is not running
Error response from daemon: Cannot kill container: fb5e5d64d231: Container fb5e5d64d23187d58c26ca0e60a6bad667b3fc2ad4ff49a3b2a81a72a986195e is not running
Error response from daemon: Cannot kill container: fd8b0e3ef6d7: Container fd8b0e3ef6d7924a9b780756289ebedff65a10dca2501c3b214d2e8cf0d86c3d is not running
Error response from daemon: Cannot kill container: 9e36439170f3: Container 9e36439170f358cfa223a1b17fdf001c64dec3f7aa614cae3c0faaef16c75e9c is not running
Error response from daemon: Cannot kill container: a1735021736d: Container a1735021736d64afcc196cb40236f7911245419f46fba00a39d5f5a84cc807f2 is not running
Error response from daemon: Cannot kill container: e100b797fb4e: Container e100b797fb4eb4b63d39df0e4b3984cb75f09209b1ad2f59d5ce5e5c37cbf4b4 is not running
Error response from daemon: Cannot kill container: 18340edac09e: Container 18340edac09e00b0dffd708072a8b3142759f9511228444be2299244327916b3 is not running
Error response from daemon: Cannot kill container: d5f5c0b70e42: Container d5f5c0b70e4215017c1e1fa84cd2e5050fb3e21f626835afcb546df1669b1e9d is not running
Error response from daemon: Cannot kill container: a69a305c0ed6: Container a69a305c0ed6a19e064deb17324b5a99f59b258fcbfe823522ebc699187a54d8 is not running
Error response from daemon: Cannot kill container: 8dc2e8212e89: Container 8dc2e8212e8957372fa5c6a2ff5f72c359dee60bfb3ee38016cd221904a0457e is not running
Error response from daemon: Cannot kill container: 8d017b7d1db1: Container 8d017b7d1db1239605dcaf8e5b517804c3bf8b760a51fba69cfb67df8b743e9b is not running
Error response from daemon: Cannot kill container: 54bcc13a7cbd: Container 54bcc13a7cbd7d5465ec30600af60b28aebfee3e21eb5cf2a4726b079a6a6ad1 is not running
Error response from daemon: Cannot kill container: 6ded8c05764c: Container 6ded8c05764c7a20561eb1b9314137de75f8c08239a11ed15fec158868abd783 is not running
Error response from daemon: Cannot kill container: a6b813499ce0: Container a6b813499ce0704cb3acebc82984af231ac94a83cc74630de79b9bcc30440524 is not running
Error response from daemon: Cannot kill container: 2893c4be9385: Container 2893c4be9385d1320c2c369de535fcbe805c4b386dc5e14ccb272ead726036e1 is not running
Error response from daemon: Cannot kill container: a64e875aa2ec: Container a64e875aa2ec3db08f518c97cf4e83dbe2413a3630b11c2c6a21c1db398ce1ed is not running