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

Build: #2139 was successful

Job: ACL one entry was successful

Job result summary

Completed
Duration
25 minutes
Revision
58760dc7d436e4c5c7720f048a99dbad850881f1
Total tests
18
Successful since
#2138 ()

Tests

  • 18 tests in total
  • 23 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  36928      0 --:--:-- --:--:-- --:--:-- 36928
Error response from daemon: Cannot kill container: 23890ed10b24: Container 23890ed10b2419af21017160c49f2bea8c06cb33d03819f5bde1c9724120e28c 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-CAOE/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAOE/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAOE/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAOE/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAOE/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAOE/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-CAOE/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-CAOE/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-CAOE/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  27370      0 --:--:-- --:--:-- --:--:-- 27370
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 323a27a7ad70: Container 323a27a7ad708341b8c210f4681c0bcb628881f22be9718d9e3ddd077981276d is not running
Error response from daemon: Cannot kill container: 4b6c7e147559: Container 4b6c7e147559ec7385a92322d1004729f75072d2a9c2ec64d1519815b9d82d71 is not running
Error response from daemon: Cannot kill container: 31f95cddeb14: Container 31f95cddeb149320f4420027812174df35c2de4d5d94f6a59b378943f01ac3f1 is not running
Error response from daemon: Cannot kill container: 03e0e1c855a5: Container 03e0e1c855a5c23c11371782d15fd0a9dff6dba1ce3b3f5a3c939b4590052270 is not running
Error response from daemon: Cannot kill container: e3e827cd556a: Container e3e827cd556a7fac371d13225b478f230a757377498b1cd850243b906d72cf92 is not running
Error response from daemon: Cannot kill container: 3a9d1a340701: Container 3a9d1a3407016cc5d7b51259e8cc7d8ff143a4ad9e8c149e88087a54c50bee38 is not running
Error response from daemon: Cannot kill container: f470a3982311: Container f470a39823112c2e63556f7aea3ee120f03adbf2a5023d25a8c1885073223214 is not running
Error response from daemon: Cannot kill container: 7c1aa5ccec9b: Container 7c1aa5ccec9b5429af051499a6c0f3b243565644eceac8873f913cdaf71e7060 is not running
Error response from daemon: Cannot kill container: 53aeb42fef61: Container 53aeb42fef610603108d3e43116681764b2df026b726af15a7b0e60bb03bc6dc is not running
Error response from daemon: Cannot kill container: c0b602620183: Container c0b602620183ee220a7d609fec5d2226d04ca83bd933219335794ca57a7b8cd8 is not running
Error response from daemon: Cannot kill container: 8a64fbdf047f: Container 8a64fbdf047f6bbff525ee6ed4877a8819fcfecd3cc7fa33a1d75e422ee42b89 is not running
Error response from daemon: Cannot kill container: 52f4501e959e: Container 52f4501e959e42a36c6d290b7fa8dc65283c0e562b9eccc4d6ae2cf37843f477 is not running
Error response from daemon: Cannot kill container: 2634fd933767: Container 2634fd9337677ac223c6d3513033f67f3e27f495f389420ce727149d39a9d4bb is not running
Error response from daemon: Cannot kill container: 896f2ab6942b: Container 896f2ab6942b6d38f7195b2997a1f63a53dfa8b02840427509ec840ae3650841 is not running
Error response from daemon: Cannot kill container: e46f351a8c71: Container e46f351a8c715113456166ce961c8e2562531b87131d76e8987fd4f0ee6293a3 is not running
Error response from daemon: Cannot kill container: d5f24a7fdf37: Container d5f24a7fdf3794b3fd3fb0218af4bee9543e91c2e7d2f49468606fbd05405791 is not running
Error response from daemon: Cannot kill container: 03522b308f95: Container 03522b308f9528f2d589164fcd8ed4502bdc968f6f52ac5d2d08d65ef173da6d is not running