RuntimeError: no "Purge archive" found in Archive row menu
request = <FixtureRequest for <Function 'test_user_sees_that_dataset_does_not_have_archive_after_purging_archive[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: 
(41 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  43083      0 --:--:-- --:--:-- --:--:-- 42688
Error response from daemon: Cannot kill container: 1fbbd2e74a5c: Container 1fbbd2e74a5cad43306a41ea3d4d017c4ab44277a4d367673a26619cb3eddc10 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
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: 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
W0526 20:27:25.466360     437 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  31020      0 --:--:-- --:--:-- --:--:-- 31228
Error response from daemon: Cannot kill container: 41318c461db6: Container 41318c461db653982369deb0734cf060588cc401f69a2c4e12c3c78b3a651041 is not running
Error response from daemon: Cannot kill container: 4e8576811fa0: Container 4e8576811fa06b736288e7849913bf68593b702210a04a51a3e978c8ffc2aba7 is not running
Error response from daemon: Cannot kill container: b22ecdfdc94c: Container b22ecdfdc94c4e4f5a7b222ed4570603c4043f7431680c424087e59cc663c8da is not running
Error response from daemon: Cannot kill container: 0f3974f1eb27: Container 0f3974f1eb273979216b07c8147dd9312201fd805dd89da5726878eec041b7aa is not running
Error response from daemon: Cannot kill container: f9580553f50b: Container f9580553f50ba2a488f0402903ed7b32ca8d8434a463696aed31b5a24f0406ff is not running
Error response from daemon: Cannot kill container: e8edb07822e9: Container e8edb07822e9ed7757acdae9092a80b68146f538c1aa48f73f1d74251ea5e188 is not running
Error response from daemon: Cannot kill container: 8c455f5277ab: Container 8c455f5277ab40d143928e43ed86840f50e6822505833e0b49dff0a2c625e5f7 is not running
Error response from daemon: Cannot kill container: bb9ce5cc0b01: Container bb9ce5cc0b01098bef9908ff9d248680ecd8843e84257f92687dff81b989d3cb is not running
Error response from daemon: Cannot kill container: 4e18fd0471ff: Container 4e18fd0471fff27eae5e817cbfcddf3265366dcb83fa39d6d470eef281e413a2 is not running
Error response from daemon: Cannot kill container: eba25bf2dc33: Container eba25bf2dc33c4bb1b92e7ae9a6e3a711d537d3d839439a9d307bb4fa0caeb31 is not running
Error response from daemon: Cannot kill container: 3faf20735983: Container 3faf20735983822ec0faf78c7733158289c01fa111ecf271106b24cebfa34900 is not running
Error response from daemon: Cannot kill container: 5b48dcf30576: Container 5b48dcf30576bf565d1ccdda54120802d4f6eab1545a612550d48ecd00217997 is not running
Error response from daemon: Cannot kill container: 825236fa286e: Container 825236fa286e88ab000168cc87513c32ee02291c701849cfdae70012632af3c6 is not running
Error response from daemon: Cannot kill container: 11c828da7e9d: Container 11c828da7e9d41a137cbcccedea3a83c1f2b64a9cbe2881fc3d89b4bf3fe0f9c is not running
Error response from daemon: Cannot kill container: 5505cb18534d: Container 5505cb18534dbf57b556cfb090eecd400cee4f01b8e42d68b16d366b3296dd04 is not running
Error response from daemon: removal of container 5505cb18534d is already in progress
Error response from daemon: Cannot kill container: 5697f5918ef4: No such container: 5697f5918ef4
Error: No such container: 5697f5918ef4