AssertionError: Hardlink tab is not active in file details modal
request = <FixtureRequest for <Function 'test_hardlink_info_is_no_longer_visible_after_hardlink_removal[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: 
(21 more lines...)

AssertionError: Hardlink tab is not active in file details modal
request = <FixtureRequest for <Function 'test_hardlink_tag_opens_file_details_modal_with_hardlinks_information[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: 
(21 more lines...)

AssertionError: Hardlink tab is not active in file details modal
request = <FixtureRequest for <Function 'test_new_hardlink_name_is_visible_after_hardlink_rename[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: 
(21 more lines...)

AssertionError: Hardlink tab is not active in file details modal
request = <FixtureRequest for <Function 'test_user_creates_hardlink_of_hardlink[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: 
(21 more lines...)

AssertionError: Hardlink tab is not active in file details modal
request = <FixtureRequest for <Function 'test_user_creates_hardlinks_in_other_directories_than_original_files[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: 
(21 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: ba63690c299a: Container ba63690c299a8f5399cdf09eb01a283a44d76e29c7c1ac7fe7aad8edbb0c8725 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-COH/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/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-COH/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-COH/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-COH/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
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]
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]
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
W0502 08:25:04.090884     438 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  17759      0 --:--:-- --:--:-- --:--:-- 17759
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: fe28a947cb05: Container fe28a947cb058327c45626a31858f07f4af924bbdaac4b98b4e7949f3226fed5 is not running
Error response from daemon: Cannot kill container: bc91b7bda84d: Container bc91b7bda84d13a1f717c512a32909cdcdbfca55d6d6bd8fdd1224fc09a6a2d9 is not running
Error response from daemon: Cannot kill container: 5bfb18dda443: Container 5bfb18dda4438e8023e56f96daf0f5cd48f2149c7bec1704d7da218792434fc5 is not running
Error response from daemon: Cannot kill container: a817bc014273: Container a817bc01427398357e1954e43229b7ef5cbfb3a4d292cf642932ffc3de678303 is not running
Error response from daemon: Cannot kill container: 5e928839bdbb: Container 5e928839bdbb66638128b3188f21c952a9e38819f48030dd4c1719e246529805 is not running
Error response from daemon: Cannot kill container: 9fc1603137e8: Container 9fc1603137e8a2d82ccc64ca070800f90c00e70b12cbeba704342e8720495bca is not running
Error response from daemon: Cannot kill container: 3e7d21915519: Container 3e7d21915519b853919af07edc6e211f2b082c875010c9bd43a06a6fafdbce7e is not running
Error response from daemon: Cannot kill container: 6bc918c5b630: Container 6bc918c5b630b0cb1623200e277222c8d47b66cbe72e22231cdb645326ce61c1 is not running
Error response from daemon: Cannot kill container: 75c1eecdb815: Container 75c1eecdb8150a55adf9eaa2daa335be7105656878570b352e673932dd5ecda4 is not running
Error response from daemon: Cannot kill container: 403e457a787f: Container 403e457a787fa121f56af95a1d60fed317ce6cd6eff89f94f2621b3b75c5f59b is not running
Error response from daemon: Cannot kill container: cfc98b0779e0: Container cfc98b0779e0695b4619b9c4e90e5412c4d5995d4d23c6f97f19ad56c1dc0fb3 is not running
Error response from daemon: Cannot kill container: e0cc61f47be5: Container e0cc61f47be511354c0da187f9310bc0a5c39b85695c76f91cfc4e5992c10ad8 is not running
Error response from daemon: Cannot kill container: a40912107f9a: Container a40912107f9a48fdfc181343ccdc5e7a28273a7dc488e593fb195e04764f24b3 is not running
Error response from daemon: Cannot kill container: fb814b71f87e: Container fb814b71f87e7027beddf4350847bfe2e4b4a03020abfd081928e38f8ada6b92 is not running
Error response from daemon: Cannot kill container: 8b8920632e77: Container 8b8920632e77a94bb1061b282af5977a27eb1aebde28e4a2483573365f2dd72d is not running
Error response from daemon: Cannot kill container: 1aed8d5b44a5: Container 1aed8d5b44a5ac888f1d888ed2b7f4e701c676bf622764eb1ad55d92837b80eb is not running