AssertionError: Synchronization is not done in given time
request = <FixtureRequest for <Function 'test_provider_with_stopped_workers_is_offline_and_resynchronises_with_others_after_restart[1oz_3op_providers_sync]'>>

    @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: 
(27 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  4658  100  4658    0     0  18037      0 --:--:-- --:--:-- --:--:-- 18054
Error response from daemon: Cannot kill container: cc3e4dc85b66: Container cc3e4dc85b66bd02b5ea90a7779b0d15a3fc66a404478050298983e96b14cacb 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
Unable to find image 'onedata/acceptance_gui:v8' locally
v8: Pulling from onedata/acceptance_gui
a1298f4ce990: Already exists
04a3282d9c4b: Already exists
9b0d3db6dc03: Already exists
8269c605f3f1: Already exists
c810ae7364ef: Already exists
78d356e6ec21: Already exists
792b20546d07: Already exists
c1d3130a77b3: Already exists
0c7ad6b015da: Already exists
114ec36e4007: Already exists
2bc588dde0c7: Already exists
89641d7ca7e2: Already exists
b6cd4b44aa19: Already exists
e1c77802a505: Already exists
f373aa611054: Already exists
Digest: sha256:97e4de524ef380ad8c07bf6c71280c378a5e0179834942ff0e6c0007d32b148c
Status: Downloaded newer image for onedata/acceptance_gui:v8
Error: Could not create /home/bamboo/.helm: mkdir /home/bamboo/.helm: permission denied
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
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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4658  100  4658    0     0  17028      0 --:--:-- --:--:-- --:--:-- 17000
Error from server (NotFound): pods "dev-oneprovider-lisbon-0" not found
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 5d76eb03a0e3: Container 5d76eb03a0e311d5fa45ef4dd7810ca233d358db67cde2b474d05f5f4893b69e is not running
Error response from daemon: Cannot kill container: 29c0edef8d3e: Container 29c0edef8d3e90f43df80223c15d45a2301b66e9854c29115f493f477b41ec42 is not running
Error response from daemon: Cannot kill container: 91cb4ff7bd13: Container 91cb4ff7bd13a947a061cacbc7eb1c1ef9684d31775f795403cdd7fb1c676257 is not running
Error response from daemon: Cannot kill container: 9fc0972af235: Container 9fc0972af2355129401050d90936b1790a9036a08e26a3898fb2d3047bcba114 is not running
Error response from daemon: Cannot kill container: 338effcdaece: Container 338effcdaece10fc46041d4073ad3e8e8b76732dcf3e04b628a064ecd68d4ebd is not running
Error response from daemon: Cannot kill container: 2748e9f72991: Container 2748e9f72991e2716542448096f1aa4ed6ca92b3f4636f2a381230b6ddcf4245 is not running
Error response from daemon: Cannot kill container: f7718606282f: Container f7718606282f930e7e30102e5fa3b1e4ba2798f9140e32b1a57ec274739cf83c is not running
Error response from daemon: Cannot kill container: c451769411ac: Container c451769411ac89a2690feacc1bcdd331e6f73a48a9eec5118d834d33e0f6a1e7 is not running
Error response from daemon: Cannot kill container: 7eed5066e545: Container 7eed5066e54559f4417816290f9ddf1d4a03180e041d87016559badd15b7b5d3 is not running
Error response from daemon: Cannot kill container: e9f620f0b29e: Container e9f620f0b29ee84c9b58618a100e1f5f32c0f6c7a337533ff6e6b61658e4e10c is not running
Error response from daemon: Cannot kill container: 293fbfa326cb: Container 293fbfa326cb9a6977ce0bb7d358ccd531da14c1dc100100ac231d0363b64b02 is not running
Error response from daemon: Cannot kill container: a1fbf21b9991: Container a1fbf21b99912aba7675353d96b2c658a541f8235a881780b163ad6fb5f352df is not running
Error response from daemon: Cannot kill container: 044fd9024daf: Container 044fd9024daf5ab4341d64d46c298de7f2c7817073809ffb8775d88c7bdd3fd2 is not running
Error response from daemon: Cannot kill container: 71fc6b2a779c: Container 71fc6b2a779c5b73448d9fbcdcb6f3ea71f19ad0ba58decc9639d6c2b024caeb is not running
Error response from daemon: Cannot kill container: c2f55419aa46: Container c2f55419aa465c50655e204c2372f899684a20f94b82559bea1320a87157b8a6 is not running
Error response from daemon: Cannot kill container: 288da6b248d7: Container 288da6b248d759f99e21bc3b8cf1780aa384e0b1f636fa83e65a5086b2fc3c7d is not running
Error response from daemon: Cannot kill container: cd017ee67a58: Container cd017ee67a5813038d87f3258dc657a4a761c19e89b7ab82c186f54dfa8e175d is not running
Error response from daemon: Cannot kill container: 562e4233e1a9: Container 562e4233e1a9d0925235b1daa21ae50d93a6096da9012c471b9f6dc8f456ce52 is not running
Error response from daemon: Cannot kill container: 38369e368af2: Container 38369e368af2b9273f3a02bfa8d1da01723909cec2e3e15824ead11baf05ad13 is not running
Error response from daemon: Cannot kill container: 3a4294214c1e: Container 3a4294214c1e7379dec0203271f321438b7c1dd60086f313125e113f391821eb is not running
Error response from daemon: Cannot kill container: 0b8dadfb7e8d: Container 0b8dadfb7e8dc4a392b344ba066e13fab054e9689410ed66f56c07f119b0cdd0 is not running
Error response from daemon: Cannot kill container: 0e473e4c5200: Container 0e473e4c5200ab42b63642d2ca828b59d9fbc9f3714130f845357bda3ca9950c is not running
Error response from daemon: Cannot kill container: 910bfafd3e4c: Container 910bfafd3e4cf718176d7ce21d3c343f98ec5b8384999706a398ba9c0d0a898b is not running