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

Build: #2151 was successful

Job: Access tokens path caveats was successful

Job result summary

Completed
Duration
18 minutes
Revision
3255e3522aecdc22fbac1ef6b15f1d9dc3564310
Total tests
10
Successful since
#2138 ()

Tests

  • 10 tests in total
  • 17 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  43896      0 --:--:-- --:--:-- --:--:-- 43896
Error response from daemon: Cannot kill container: 71b85a9aa56d: Container 71b85a9aa56d5f0be9d3775283fd958a0cf6f6c35f248a924e1c4d6aa4356f7a 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-CATPC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATPC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATPC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATPC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATPC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATPC/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-CATPC/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-CATPC/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-CATPC/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  40815      0 --:--:-- --:--:-- --:--:-- 40815
Error response from daemon: Cannot kill container: e9d57da8f3df: Container e9d57da8f3dfc1dbfec4fbeabcb6537157060a9d3cd6ad06fea0a0452713abc2 is not running
Error response from daemon: Cannot kill container: 15f0abefc67f: Container 15f0abefc67f2cac88cb9ae825fce9ca5aa9c0d49937f34e5bc0f86d600637bb is not running
Error response from daemon: Cannot kill container: 815019e254d5: Container 815019e254d5b85a0e529fbd7fdc0051cda5b6ae6d02ea007e3ff76a1f27ac12 is not running
Error response from daemon: Cannot kill container: f71cb4d02177: Container f71cb4d02177abc0028feb97c29eea193f497c591f831af3bb06f68f3cdc40b7 is not running
Error response from daemon: Cannot kill container: 64e314907b1e: Container 64e314907b1e174164507071d36f404e6ff756601bc49da504ddc1407bbc79a3 is not running
Error response from daemon: Cannot kill container: f72dbed60ba9: Container f72dbed60ba9a0f5e84481ef23cac50e6b7a56310d034a3da6994a891c745e75 is not running
Error response from daemon: Cannot kill container: 4422414bb7e7: Container 4422414bb7e7f3eb22a0e4b097fd5bd53d7b89fcdb05db97086e70f57469721b is not running
Error response from daemon: Cannot kill container: 9c540a850f5f: Container 9c540a850f5f0c8591b22b96b07f649935b3f73432332665de05cc1a774d5bbc is not running
Error response from daemon: Cannot kill container: 8bc5eeee688b: Container 8bc5eeee688b213abc295eeae4960cee7c35b33490c795726d4c428b42ced638 is not running
Error response from daemon: Cannot kill container: 0050383e1c43: Container 0050383e1c4344a1f9f9ee0e6ad88224b6804856bcb827be03250dcf707fd6b9 is not running
Error response from daemon: Cannot kill container: 9ed7fe877991: Container 9ed7fe8779918d25b85868b3059ce31b56f399e3a8d772a5827e97d2a8778c9c is not running
Error response from daemon: Cannot kill container: 245d30d56ffc: Container 245d30d56ffc2beca053ef418656e3857e2f42ea4de7191369f419fe7381c05b is not running
Error response from daemon: Cannot kill container: 5df32755a4ac: Container 5df32755a4ac8807a5bf25c2b2191412baa61315041fb1951c5230df9105a01e is not running
Error response from daemon: Cannot kill container: af30e4b318f2: Container af30e4b318f214702bb72981e85ca7a1d0e0c386c155e37d0cd9740ac95ce499 is not running
Error response from daemon: Cannot kill container: a92b479e05cb: Container a92b479e05cbb5d3840d335b0ad18d23466365d4dcc06e797b5f250f5615735e is not running
Error response from daemon: Cannot kill container: c013de8a0afa: Container c013de8a0afa1f969b953ae16f8675ee4b1fbb496321a13436d4b0fb5918653c is not running
Error response from daemon: Cannot kill container: af98e649e897: Container af98e649e897c3de3be0a235f09a6386d4dd92ed7c42e5e0a9f57cd189040ae9 is not running