AssertionError: file upload not finished within given time
request = <FixtureRequest for <Function 'test_user_sees_file_is_not_visible_after_its_upload_has_been_canceled[1oz_2op_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
100  4419  100  4419    0     0  10883      0 --:--:-- --:--:-- --:--:-- 10911
Error response from daemon: Cannot kill container: 7ca629e97f20: Container 7ca629e97f2015b8969f50db7e1cec8a3eadbd7f360ee6d296dfe9fbc92e5129 is not running
tput: unknown terminal "unknown"
Cloning into 'bamboos'...
Cloning into 'cdmi_swagger'...
Cloning into 'one_env'...
Cloning into 'onepanel_swagger'...
Cloning into 'bamboos'...
Cloning into 'oneprovider_swagger'...
Cloning into 'bamboos'...
Cloning into 'onezone_swagger'...
Cloning into 'bamboos'...
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error: Could not create /home/bamboo/.helm: mkdir /home/bamboo/.helm: permission denied
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
2021-02-08 13:44:23,732 WARNING Received response with both Content-Length and Transfer-Encoding set. This is expressly forbidden by RFC 7230 sec 3.3.2. Ignoring Content-Length and attempting to process response as Transfer-Encoding: chunked.
2021-02-08 13:44:23,732 WARNING Received response with both Content-Length and Transfer-Encoding set. This is expressly forbidden by RFC 7230 sec 3.3.2. Ignoring Content-Length and attempting to process response as Transfer-Encoding: chunked.
2021-02-08 13:44:23,732 WARNING Received response with both Content-Length and Transfer-Encoding set. This is expressly forbidden by RFC 7230 sec 3.3.2. Ignoring Content-Length and attempting to process response as Transfer-Encoding: chunked.
Error: Could not create /home/bamboo/.helm: mkdir /home/bamboo/.helm: permission denied
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
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  4419  100  4419    0     0  16164      0 --:--:-- --:--:-- --:--:-- 16186
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: ac10852a2b09: Container ac10852a2b09e16a48b0be620e3a694644035a663fa0d8d5c03d92e07804bbb1 is not running
Error response from daemon: Cannot kill container: ae6782dd52ae: Container ae6782dd52aee3eaa34c0766843e8908c1100bfd87f1c295168fd18feebfc72c is not running
Error response from daemon: Cannot kill container: 21f4201cad3f: Container 21f4201cad3f02fbe77ace7955e5df04f9abfb61ad565ac5497d9ae9d66e43fe is not running
Error response from daemon: Cannot kill container: f8b1a89e3f9e: Container f8b1a89e3f9ec28794f669190019adef86b362943a204bc99c9f3d3bf69be3a1 is not running
Error response from daemon: Cannot kill container: f76ef4423afa: Container f76ef4423afa4a35e8de73095a68dcafe6254b01f49e228a4caeb5f046b769f7 is not running
Error response from daemon: Cannot kill container: 9659c0bbc9bd: Container 9659c0bbc9bda596f4c7b18d627a1b1a718da039935767e1080dcb6aaa44c712 is not running
Error response from daemon: Cannot kill container: 9c9e387e047a: Container 9c9e387e047a24019205420de2748f9745655bdd6aed9247c1ccfe5ffaa38972 is not running
Error response from daemon: Cannot kill container: 2b6e0cf77c5c: Container 2b6e0cf77c5c80b26b500c3a1bf4c120ff73dededb6d08e5a3fc7856c6c73be7 is not running
Error response from daemon: Cannot kill container: 9268305ba534: Container 9268305ba5340db3943e882d3c28fc2624ada3560773337641e6cb62876b71f5 is not running
Error response from daemon: Cannot kill container: 2f913f23418a: Container 2f913f23418a0ffc2c9a6304f2640d2fee3f85ab40f806589886a6b0c63277ee is not running
Error response from daemon: Cannot kill container: c7a21cb9bf1c: Container c7a21cb9bf1c6b68c60d210808c2873316027c5e6c1f5ee2bd5d07d1407a5a7c is not running
Error response from daemon: Cannot kill container: 8fbd28cd92ad: Container 8fbd28cd92adead1ab72241ee0f1783237935c771db5e2e55517a1146eff1d8f is not running
Error response from daemon: Cannot kill container: 95300150935b: Container 95300150935b112783a71931c2e629248af2211edfa88a8f22d8156c48682de7 is not running
Error response from daemon: Cannot kill container: 78e9b27e6d6c: Container 78e9b27e6d6c4655270157dff53d81476f7e7bc2518759ca483c120a3d0a5545 is not running
Error response from daemon: Cannot kill container: de9f4e3cb8f9: Container de9f4e3cb8f99e2d29f99021a635200c32339eabe544c07b330495ca39ebb4d6 is not running
Error response from daemon: Cannot kill container: 2c1b5dcf22d6: Container 2c1b5dcf22d66b2b9349d46825a67d9446d946a8ba187700efb9be35b06ede89 is not running
Error response from daemon: Cannot kill container: c5b01486cf5c: Container c5b01486cf5cd0f207cfcab498a4a5afa472ba38a257facf4aafdda42a845aa7 is not running
Error response from daemon: Cannot kill container: f4e78fade7e7: Container f4e78fade7e74508b5ea427957070898d6496fe1395242aef47838480e4b0815 is not running
Error response from daemon: Cannot kill container: 6f9a06d2e1b1: Container 6f9a06d2e1b15e744bea8e3baf83f31d9f5cebb204ca0d5f42fb9538936b81f9 is not running