Acceptance tests using different clients concurrently. Environment deployed from packages.

Build: #2066 was successful

Job: Files movement was successful

Job result summary

Completed
Duration
18 minutes
Revision
3e5c43f6031850a5b683dcd8e77025ff37a3eaac
Total tests
16
Successful since
#2002 ()

Tests

  • 16 tests in total
  • 16 minutes taken in total.

Error summary

The build generated some errors. See the full build log for more details.

  % 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  45617      0 --:--:-- --:--:-- --:--:-- 45617
Error response from daemon: Cannot kill container: 85a3e997b439: Container 85a3e997b43983b57018234ba0a0ccc68ee6fe74b62982b5e371b99b59f376f4 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-MAOPT-CFMT2/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CFMT2/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CFMT2/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CFMT2/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CFMT2/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CFMT2/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-MAOPT-CFMT2/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-MAOPT-CFMT2/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-MAOPT-CFMT2/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
/bin/sh: 2: [[: not found
Error: could not find tiller
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
id: ‘user1’: no such user
command terminated with exit code 1
id: ‘user2’: no such user
command terminated with exit code 1
command terminated with exit code 1
command terminated with exit code 1
command terminated with exit code 1
id: ‘user1’: no such user
command terminated with exit code 1
id: ‘user2’: no such user
command terminated with exit code 1
command terminated with exit code 1
command terminated with exit code 1
command terminated with exit code 1
Defaulted container "oneclient" out of: oneclient, wait-for-onezone (init), wait-for-token-dispenser (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
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  48468      0 --:--:-- --:--:-- --:--:-- 48468
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 96f8f793bcef: Container 96f8f793bcefca8020a5cba29cdc56846960c61bd2f4be195aabb7dcd351a1bd is not running
Error response from daemon: Cannot kill container: 9a7f527387af: Container 9a7f527387af052347306007e11b82d16e88e951fc44497175c63df54e99190f is not running
Error response from daemon: Cannot kill container: b622b70fac8e: Container b622b70fac8e00b837067f808331a58ff927389e6f0fc7e5c24976b5842af791 is not running
Error response from daemon: Cannot kill container: bffa4e443045: Container bffa4e4430451fd88ada581e2f3e3a8005cf7a1bafa3c1881d81f358296d93de is not running
Error response from daemon: Cannot kill container: ad79e4366c0c: Container ad79e4366c0c0a93cce1612128ca480c6fc3e20753543999abe17470201761fc is not running
Error response from daemon: Cannot kill container: 89e72b51292a: Container 89e72b51292a3c848d2d640d7a92d1919f1c9d9569e57c906b273467ac263633 is not running
Error response from daemon: Cannot kill container: 771938dc3b21: Container 771938dc3b21e057d1a15208bf85be16ee9ed49ba02c9473a128be9531d29618 is not running
Error response from daemon: Cannot kill container: 9a770c75ff01: Container 9a770c75ff01e503ee2d372a94d92aadd68eb70e84673e948c3561e48eff729b is not running
Error response from daemon: Cannot kill container: 49ba8e6a203d: Container 49ba8e6a203dbdd09b56b9f62e2d689d3161e0680dadc095de96128772e0d729 is not running
Error response from daemon: Cannot kill container: 016f492097de: Container 016f492097ded01215f7b619941508a336e85c2566cba1f3a7400243013f7fea is not running
Error response from daemon: Cannot kill container: ad13060ded74: Container ad13060ded741418d629f05aa116040a7aad84e1b470e4c0ffee05ed009a6873 is not running
Error response from daemon: Cannot kill container: e0dff4f4c090: Container e0dff4f4c0905a491f833fe8090f3908dade2ec3b7159e45a1e28e8c0a3dfbd9 is not running
Error response from daemon: Cannot kill container: 601ec9b50846: Container 601ec9b50846f834f9d163a9df12c58584f12c37e109b50b80ac1dc31b75703b is not running
Error response from daemon: Cannot kill container: 2074e7ce739a: Container 2074e7ce739a933e6a3e31becd9ad77f85c863d1aede3116b2cdd4e19304751e is not running
Error response from daemon: Cannot kill container: bcf0a73c9c96: Container bcf0a73c9c96cdde518497b7ce389d9bcea67eefa56a62efc6e83bfc707e6997 is not running
Error response from daemon: Cannot kill container: e5d7c222dd9b: Container e5d7c222dd9bdb554a0613c9250207e56c1ac706b168a6afbe3fd58809a7676b is not running
Error response from daemon: Cannot kill container: 41b0cf0aed0f: Container 41b0cf0aed0fcf20a2e3d79d3f1d37c16b79ae27207f10cbbcc26728a846d69e is not running