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

Build: #2138 failed

Job: Tokens was successful

Job result summary

Completed
Duration
9 minutes
Revision
e0d41fc6d1fe8d12a3b45aa43e3371e982734e6e
Total tests
6
Successful since
#2117 ()

Tests

  • 6 tests in total
  • 8 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  44740      0 --:--:-- --:--:-- --:--:-- 44740
Error response from daemon: Cannot kill container: 0fdf85c72a3f: Container 0fdf85c72a3fa79504c5e2b1749078965f9369289b2679c1da5ea50ffb75fbdf 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-CTT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CTT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CTT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CTT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CTT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CTT/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-CTT/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-CTT/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-CTT/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  47000      0 --:--:-- --:--:-- --:--:-- 47000
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 8cda3f6849d8: Container 8cda3f6849d800704c0b2848459555270d9855384696cf985f9d76427b4adda3 is not running
Error response from daemon: Cannot kill container: 302c2058187b: Container 302c2058187b6fc4fb1364a16633dfa8b454681a4e0c2b3b40807c72d6fd54fc is not running
Error response from daemon: Cannot kill container: 93055de9a1a5: Container 93055de9a1a56ddcc576f9000142095584323d8407b565c11f5067daffffa072 is not running
Error response from daemon: Cannot kill container: e32430cd398f: Container e32430cd398fcfed92038eb2ff4bd72f2ef88ba51d361e775feb8e5c339c0dfc is not running
Error response from daemon: Cannot kill container: 31e4e8fa08cd: Container 31e4e8fa08cd0050a2c041204fde2a4d4c3ea83b60092a72b58ae5a0768f031a is not running
Error response from daemon: Cannot kill container: beb5ece0fc83: Container beb5ece0fc83caa2651cb3978c90a264727f2803990d0b12aa985ee51c835a0b is not running
Error response from daemon: Cannot kill container: 826da001b2ad: Container 826da001b2ad466a78bb756a9d1d36f53b6ef779dca011697b186239341d0ec1 is not running
Error response from daemon: Cannot kill container: b77edfed312a: Container b77edfed312a5cc9d11504d0e8c734d95f037a7025819370465e97e741549079 is not running
Error response from daemon: Cannot kill container: f2e28d848ed1: Container f2e28d848ed19229db61f929b460d81d1af4eb5c6e514ac2cdd5ea5ad370bb05 is not running
Error response from daemon: Cannot kill container: 13b613857e7f: Container 13b613857e7fc5273ba06de129158c209d8926d3fc842643cfb45b81907deafc is not running
Error response from daemon: Cannot kill container: 0e73f9ababe2: Container 0e73f9ababe213037b2f98161e107e838fbf969ba5431fd64c2e62dd35df184c is not running
Error response from daemon: Cannot kill container: a1dbdfc6a3a7: Container a1dbdfc6a3a7edf184e38784957f9b0faf998f30b362a1cb301a45d41d0f5380 is not running
Error response from daemon: Cannot kill container: ee98771f2aa3: Container ee98771f2aa306649225b5174691c29a2fe58b592eb8eab0b84fd041968ba870 is not running
Error response from daemon: Cannot kill container: f48d740b4d1f: Container f48d740b4d1f2097f03603bf1f6e9e2156f5b245ae7782c379448dd651b16bfb is not running
Error response from daemon: Cannot kill container: 01c5b5459f6d: Container 01c5b5459f6db335751b937a08e42304a9b110b393803d101a55613b3346fca3 is not running
Error response from daemon: Cannot kill container: eacb8c866ab1: Container eacb8c866ab1d491508002f844243d92d09d4e3cd33097d5ba3df36cdfbb6a4c is not running
Error response from daemon: Cannot kill container: 8632374273d8: Container 8632374273d8374f60518280b36e98875921d546b58057ce2378cdf1a2b23621 is not running