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

Build: #2066 was successful

Job: Directories movement was successful

Job result summary

Completed
Duration
33 minutes
Revision
3e5c43f6031850a5b683dcd8e77025ff37a3eaac
Total tests
20
Successful since
#2047 ()

Tests

  • 20 tests in total
  • 30 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  33000      0 --:--:-- --:--:-- --:--:-- 33000
Error response from daemon: Cannot kill container: c6794529d32d: Container c6794529d32de6553308689ed34d723c42120a24f7a63db19ad3b726f249b38e 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-CDMT2/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDMT2/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDMT2/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDMT2/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDMT2/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDMT2/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-CDMT2/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-CDMT2/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-CDMT2/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  45617      0 --:--:-- --:--:-- --:--:-- 45617
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 9e8db781a55e: Container 9e8db781a55ec1eb928bdcf4c699a201d2aa3832d2d5dea74f0ffae307c6daa6 is not running
Error response from daemon: Cannot kill container: 63e9dd6b5532: Container 63e9dd6b5532a9e193b94953830c19d0b12aa3829b7c56bd67e1fae7539941ce is not running
Error response from daemon: Cannot kill container: effb3ea451c5: Container effb3ea451c509a74c8d254736e72502ed6970fa720d29e4eaf769572121d700 is not running
Error response from daemon: Cannot kill container: ba23355de7ad: Container ba23355de7ad20d5bbbf07a9fd929749208c5701d5dde6f7c63c85484ce50a06 is not running
Error response from daemon: Cannot kill container: fd1300331f92: Container fd1300331f927d814f71e99429e37d86854bc2065d4549ba813179402b1911ae is not running
Error response from daemon: Cannot kill container: 90a21a7fe749: Container 90a21a7fe749b90767749fdcb44285c447cf3139280266e77e8a9d7ec5358737 is not running
Error response from daemon: Cannot kill container: 014e2a04e2ac: Container 014e2a04e2acca016c8ae91ccc5a8a3f2ea2713f1153b42048dad3c8fddf7744 is not running
Error response from daemon: Cannot kill container: 03e6fa7f4b52: Container 03e6fa7f4b526135a83385b540be742d7ed33cbe1078958e3739daa34f83803e is not running
Error response from daemon: Cannot kill container: 15aa84699f30: Container 15aa84699f30934f50b91d5c4bcbbb9bd8bb32d97c59d8da2b168696f0b1c839 is not running
Error response from daemon: Cannot kill container: 0c2d999d55d7: Container 0c2d999d55d75f5781eaa81bcf20fbb6cf03585c7882b6a394ddf0c473190144 is not running
Error response from daemon: Cannot kill container: 2fe4f51aa2be: Container 2fe4f51aa2beff5d1c7603f0f8f9e5783e36f2305a6cb76cadcafde1dd1f7f47 is not running
Error response from daemon: Cannot kill container: b0ae4254cb6a: Container b0ae4254cb6a6a7c2ac25f023a982a2fdccb122377f8775a2a7a9a8687186f74 is not running
Error response from daemon: Cannot kill container: 872e6023dc64: Container 872e6023dc647912bcd49ffa47c11595ba77a5cba8cff5200bb949f9826ddd3f is not running
Error response from daemon: Cannot kill container: ca2bcd2eaa8e: Container ca2bcd2eaa8ef1b548531e36a79c4adb2c87804ba13814716239f332b91734c4 is not running
Error response from daemon: Cannot kill container: 1aa7122f50a1: Container 1aa7122f50a1a68baea14b11ee79b3c784cc80948789a92661da02eb1ddcd439 is not running
Error response from daemon: Cannot kill container: 5ff592936cdf: Container 5ff592936cdf9b97cf1788bb41719322dce59de08a4e542d29d20071b28bbf24 is not running
Error response from daemon: Cannot kill container: 090cd27c3b99: Container 090cd27c3b993a622f006c3a7e71619b618bb0aa58f3e2d2b4fd1576981025a6 is not running