AssertionError: displayed 4 as number of updated files on sync chart instead of expected 3
request = <FixtureRequest for <Function 'test_user_configures_storage_sync_and_sees_storage_synchronization_statistics[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  44740      0 --:--:-- --:--:-- --:--:-- 44740
Error response from daemon: Cannot kill container: 82201c1077c9: Container 82201c1077c9b205401569311404aa2437f374aa608f841eddf2e2dc700149c0 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-CSSC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/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-CSSC/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-CSSC/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-CSSC/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: 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 find tiller
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]
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
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
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
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
W0819 20:09:02.577097     716 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  28030      0 --:--:-- --:--:-- --:--:-- 28200
Error response from daemon: Cannot kill container: 7312a48e1655: Container 7312a48e1655703becc9424e2e5f30e521eb23e24ae675dffa4c4c6a815bdde9 is not running
Error response from daemon: Cannot kill container: 2d31d5e27357: Container 2d31d5e273575b349896fa69bf0820b722e587f7896d7e8d48f8c0dda96b578e is not running
Error response from daemon: Cannot kill container: 8ca9372414f6: Container 8ca9372414f688fcbd007c4eecc4fa03ed396eadddd64346a065d525c9ed959a is not running
Error response from daemon: Cannot kill container: f07a12b62fbb: Container f07a12b62fbb166329b258fda987eb695e1474e581866b44863b566ea9879b5d is not running
Error response from daemon: Cannot kill container: 975cd0c65052: Container 975cd0c65052ae8cf4275fabfafc61639edb179708dda720dd087ee8b5b3a144 is not running
Error response from daemon: Cannot kill container: 36d12c59a8f5: Container 36d12c59a8f5f05b9170a8cbd5ffe5d2c064bb5a804f8949d21d43890be5cd6a is not running
Error response from daemon: Cannot kill container: 7c5aba6c370a: Container 7c5aba6c370a23e3c27c777e91d47d0437b9882a02e4045925d30b745c7cf96c is not running
Error response from daemon: Cannot kill container: f7967efc236e: Container f7967efc236ecea8e27baf30911ec1b1a77faa32705d3d8e994e073ad2b4028e is not running
Error response from daemon: Cannot kill container: b7f345568c9b: Container b7f345568c9b4c428474483fab1082ed27314a045d4280fa773410dc545e3539 is not running
Error response from daemon: Cannot kill container: 27d3039f556d: Container 27d3039f556d36a22a74773b030c01b967c58b5d0daf7ad4f351c65b22c593a3 is not running
Error response from daemon: Cannot kill container: 0cc66257da21: Container 0cc66257da21cecf0159f2ad70da6f087e495e9a73db7c20c886cecf72e9dc81 is not running
Error response from daemon: Cannot kill container: fd2e3775ea61: Container fd2e3775ea61b906dd921967a72586dccd5e30cc93b66651a52e87f53f340e4c is not running
Error response from daemon: Cannot kill container: d517b2187551: Container d517b2187551291cf58e4c3dfc1d754c042c4b9ec0b03ffb2e1919003021c185 is not running
Error response from daemon: Cannot kill container: 426ac4f35860: Container 426ac4f3586078a4a805898647a3bd4e04e5fad97bb2f73be23e30523f575ac4 is not running
Error response from daemon: Cannot kill container: c5716850a50b: Container c5716850a50b4857ebc89eadc35838d78466f4c51f3c63879fe250c8b87cc397 is not running
Error response from daemon: Cannot kill container: 264527143a89: Container 264527143a89102c9cc08cc9a84169ba4abf2de9b33991b9f910537fcae0c9c9 is not running