tests.utils.http_exceptions.HTTPInternalServerError: [500] Internal Server Error: {"error":{"id":"internalServerError","description":"The server has encountered an error while processing this request."}}
request = <FixtureRequest for <Function 'test_user_changes_provider_name_and_domain[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: 
(53 more lines...)

tests.utils.http_exceptions.HTTPServiceUnavailable: [503] Service Unavailable: {"error":{"id":"noConnectionToOnezone","description":"No connection to Onezone."}}
request = <FixtureRequest for <Function 'test_user_deregisters_provider_registers_it_again_and_sees_that_provider_is_working[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: 
(53 more lines...)

RuntimeError: no "space3" found in DataPage in Onezone page
request = <FixtureRequest for <Function 'test_user_sees_that_synchronization_autoupdate_still_works_after_changing_mount_point_for_storage[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: 
(43 more lines...)

RuntimeError: no "new_storage2" found in StorageContentPage in content in Oneprovider Panel 21.02.0-alpha8
request = <FixtureRequest for <Function 'test_user_uploads_files_on_freshly_supported_space_on_newly_created_storage[1oz_1op_deployed-browser_emergency-new_storage2]'>>

    @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: 
(39 more lines...)

RuntimeError: no "new_storage1" found in StorageContentPage in content in dev-oneprovider-krakow Oneprovider Panel 21.02.0-alpha8
request = <FixtureRequest for <Function 'test_user_uploads_files_on_freshly_supported_space_on_newly_created_storage[1oz_1op_deployed-browser_unified-new_storage1]'>>

    @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: 
(40 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  16399      0 --:--:-- --:--:-- --:--:-- 16459
Error response from daemon: Cannot kill container: 0f228dae6970: Container 0f228dae6970650238f21834cea85e6581ef884325a6a420baed8b11a0392644 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  15564      0 --:--:-- --:--:-- --:--:-- 15526
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 5629c96efa89: Container 5629c96efa89e7df81a9539a3794fe4a5500c378928579f25bfd07ab910e105e is not running
Error response from daemon: Cannot kill container: 5e1e87ed9cfd: Container 5e1e87ed9cfd025635ff5586475a1254d35335c9fe7df5f505cf85e5763f73b0 is not running
Error response from daemon: Cannot kill container: 8db3ff8bc169: Container 8db3ff8bc1697256c9aa8ea7ec7f7d970100fdc6e6d2cae92015f99ad08c7275 is not running
Error response from daemon: Cannot kill container: 1864690935c7: Container 1864690935c786d79840bb46f212e286b92ee3c6c5a1ec8e089a2c2f9eb9458b is not running
Error response from daemon: Cannot kill container: 7feef967019a: Container 7feef967019a878c847c315d6158339000d277ceb166d5acdafff1cc149dc7ba is not running
Error response from daemon: Cannot kill container: 0171d0091573: Container 0171d00915736649d2e37291575c5f9089bdf64088eaf3cef3042c6b2b5dfdba is not running
Error response from daemon: Cannot kill container: cf9fa1d03b74: Container cf9fa1d03b746a2248ed3fccaa15d3726f4c624b8d17df818c7e68833e238738 is not running
Error response from daemon: Cannot kill container: 8a9372db4979: Container 8a9372db49798bfc93d5b15a1f72a6ca9865fb4b0b323ac988eaed7334739845 is not running
Error response from daemon: Cannot kill container: 6e7501dc11bb: Container 6e7501dc11bb9c12a375c1a453f1de121a846a09662cc4f3a00703698ec34bd4 is not running
Error response from daemon: Cannot kill container: 96e9eaefb70f: Container 96e9eaefb70f538633380a62f29fee9bf7facaf2433c6b5a78bbb4b719cfe99c is not running
Error response from daemon: Cannot kill container: 3978cee0a9e4: Container 3978cee0a9e4613fed0e2458412b36d362923e4373933569a480baaa45b344a2 is not running
Error response from daemon: Cannot kill container: 4063f0aed39c: Container 4063f0aed39cc9516cadfea042183454c37a2cdeecd1a2c1ec0cfc000676a975 is not running
Error response from daemon: Cannot kill container: 2b512376f245: Container 2b512376f245408b91fbba2b0d80db2ad5cbccf78ca49c15f04ecbda23339952 is not running
Error response from daemon: Cannot kill container: fab626c73aed: Container fab626c73aed4e6957d3be8f459ef076d5cbeeac91f63d817fb965846500ad3a is not running
Error response from daemon: Cannot kill container: c4fc81378fbc: Container c4fc81378fbcc28b09cfa6f42de05d9d8c2a91eeba15dfc4125c5f0a25794fc3 is not running
Error response from daemon: Cannot kill container: 65af82414669: Container 65af82414669c63b066dd8a31ec2249e55cef0bd584cec10b57db28123a63693 is not running