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

Build: #2128 failed

Job: QoS was successful

Job result summary

Completed
Duration
6 minutes
Revision
18bc64d62a08509d59724b954e5560cec0d40f3f
Total tests
4
Successful since
#2117 ()

Tests

  • 4 tests in total
  • 4 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  48468      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: d409cc669899: Container d409cc669899ca9aa6439f7440c49134725e9b814901e3d736511982625223bd 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-CQT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CQT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CQT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CQT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CQT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CQT/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-CQT/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-CQT/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-CQT/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)
rsync: change_dir#3 "/tmp/logs" failed: No such file or directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at main.c(819) [sender=3.1.2]
command terminated with exit code 3
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  43083      0 --:--:-- --:--:-- --:--:-- 43083
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: cd51579bf7ca: Container cd51579bf7caa5b57900eb77aeb3c92561807132ac0fc8b123107e10c5807b1d is not running
Error response from daemon: Cannot kill container: b292ab5d0272: Container b292ab5d0272cf448dd28ef4d5483cfe1e513b1e396da38f0ebfa7ffb7a873de is not running
Error response from daemon: Cannot kill container: 2b2ec4f872da: Container 2b2ec4f872dac52fed165f054f6745256e3a2633c68d3e30325588e5d81b39dd is not running
Error response from daemon: Cannot kill container: befc19052180: Container befc19052180a08e3025f3e1a1b20d9db036aac8904f50dbbe388a24bcf7c444 is not running
Error response from daemon: Cannot kill container: be1d8b0d01ea: Container be1d8b0d01ea0a1c56f83067f58f7559749f61b6ce46979547cebea8843044ba is not running
Error response from daemon: Cannot kill container: 95f609dbca4f: Container 95f609dbca4f9197d5c08d5544675388cd54886ebc3ad3157331eecfac273efe is not running
Error response from daemon: Cannot kill container: 2d6d2fa48eff: Container 2d6d2fa48eff9fd7b698719785f946d3a8dac48e779dfca0a48916f1da98afd1 is not running
Error response from daemon: Cannot kill container: be8ed7683d43: Container be8ed7683d4379a889a9f4a66c7fb758c58cf5586ffc668e5aba83954e5f2e3e is not running
Error response from daemon: Cannot kill container: 1bd19cc265e8: Container 1bd19cc265e8b1cfc7e89575d183e99115e928702e553cd5db69e24067fcb8cf is not running
Error response from daemon: Cannot kill container: ce506c87b061: Container ce506c87b061d2cca5e265460e138b3b4f203b221b0d76c6bb20a5a1c7f9a828 is not running
Error response from daemon: Cannot kill container: 729198e4dbff: Container 729198e4dbff8d81780201a56bb90ff6a50853bfbd7abf639fc90d700173ec63 is not running
Error response from daemon: Cannot kill container: f0436fb60ef0: Container f0436fb60ef0cbc642a889b4e88673379755d5bb20a530f783dd38f28efecb99 is not running
Error response from daemon: Cannot kill container: 4f088268ae43: Container 4f088268ae435711980be6fc48076c9b58c667c81f565bd824ca21d91b852004 is not running
Error response from daemon: Cannot kill container: e8baad8a364d: Container e8baad8a364dbedbf22f37540c899043d41468ef9662c4347e2e0fc7314c00f3 is not running
Error response from daemon: Cannot kill container: ff8641243fc7: Container ff8641243fc737ed143524a2041152b6e3282fde8cacad4656544b139ad7d58e is not running
Error response from daemon: Cannot kill container: 793aafd90a3f: Container 793aafd90a3f8c1bf6a0efbb5ca567f6c3dd86144a56ba0eeb59b78618a8a119 is not running
Error response from daemon: Cannot kill container: b3f1fee01bdc: Container b3f1fee01bdcf70bd95891aab7b33128e003330b408de2bec02f066d06add693 is not running