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

Build: #2125 failed

Job: Archives was successful

Job result summary

Completed
Duration
34 minutes
Revision
18bc64d62a08509d59724b954e5560cec0d40f3f
Total tests
25
Successful since
#2117 ()

Tests

  • 25 tests in total
  • 21 tests were quarantined / skipped
  • 31 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  39769      0 --:--:-- --:--:-- --:--:-- 39769
Error response from daemon: Cannot kill container: e6a49c1eaca0: Container e6a49c1eaca0e7114c7c2356db55a1e8f614380a0520072a08295e6db3599abe 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-CAT3/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAT3/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAT3/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAT3/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAT3/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAT3/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-CAT3/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-CAT3/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-CAT3/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  45174      0 --:--:-- --:--:-- --:--:-- 45174
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 65ae496924d6: Container 65ae496924d6a9e5298cffbd8835f74e4d46af81ed81112a7b43a184d5a037f3 is not running
Error response from daemon: Cannot kill container: f4e701ca00d5: Container f4e701ca00d5a213f420267e62ef4d2fc419dc132983b524f53cdf877d96e6f4 is not running
Error response from daemon: Cannot kill container: caf37972670d: Container caf37972670d8cddfb9323bac4c4c55f83a51a6214c4123ff4edddb3d96f40ec is not running
Error response from daemon: Cannot kill container: 3427dc5d8f40: Container 3427dc5d8f40adc7e0db1958af609cae5dd760730d34d1429c5be203fed0f49b is not running
Error response from daemon: Cannot kill container: 6700cfba1e33: Container 6700cfba1e334a64aa55111c5d55fc8a16eee9062f3b34e7e55d615331bbaa92 is not running
Error response from daemon: Cannot kill container: 7a0896c1befc: Container 7a0896c1befc1b4a2c76672dace29d6e0b2135a17e8f7f8792176bf7b35dc18b is not running
Error response from daemon: Cannot kill container: 923e6238b7e1: Container 923e6238b7e1013d2dd965eca35b741399441448c6bc5d9953ac9c93d91edb87 is not running
Error response from daemon: Cannot kill container: c499e9263d30: Container c499e9263d3078562e12340d94a745b64d33f284fac2d63e0f593fcc6d91214d is not running
Error response from daemon: Cannot kill container: 168a6be980ac: Container 168a6be980aca41b719b9e4036224619ae64e276f826072335f87c5caf6a0be4 is not running
Error response from daemon: Cannot kill container: a532cf84aa54: Container a532cf84aa543ecfcf634e88f26bb912ec0c9552382e0a7d5e92fb5a54d8e5db is not running
Error response from daemon: Cannot kill container: b87e950dadc9: Container b87e950dadc94506688d79750ef719ac73d996973f97086b71fcdea40852055f is not running
Error response from daemon: Cannot kill container: 0b8f943d45fd: Container 0b8f943d45fd8870371ab5f14f6e21199caef7431284f813c470a3e686da6730 is not running
Error response from daemon: Cannot kill container: 98c739e62412: Container 98c739e6241223d43c95547b4faff9b794b74be2a43aa53833214ea5fcadc1e3 is not running
Error response from daemon: Cannot kill container: 68f19ad4f08e: Container 68f19ad4f08e546c3d918c1cbe09b0ac36a90adb4a3e4d59808df6bbb7583884 is not running
Error response from daemon: Cannot kill container: 37b6ac5dc8b8: Container 37b6ac5dc8b87abebc6920b9fa0035ac8f51fc677c253e01be1c7033d37541aa is not running
Error response from daemon: Cannot kill container: 8a36b47ee9ca: Container 8a36b47ee9cae8102412d49c5da5682ceefd0ee676de6b5d51ec498081410aaf is not running
Error response from daemon: Cannot kill container: 432efb7964e9: Container 432efb7964e91b897e474963dc6ebe556b741102af1b408c4362210afea41540 is not running