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

Build: #2143 failed

Job: Directories remove metadata was successful

Job result summary

Completed
Duration
16 minutes
Revision
9f3f7d13ff3170843d2426195d2f9fecb6f10db3
Total tests
18
Successful since
#2138 ()

Tests

  • 18 tests in total
  • 15 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  46530      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: 69f18ebd7ac9: Container 69f18ebd7ac913a6a8eb20edcfca78c25ced982f91bc90a98406f6a83a292d6b 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-CDRM/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDRM/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDRM/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDRM/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDRM/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDRM/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-CDRM/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-CDRM/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-CDRM/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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  48468      0 --:--:-- --:--:-- --:--:-- 47969
Error response from daemon: Cannot kill container: d0b3a310dc4e: Container d0b3a310dc4ec4cdc92686e0aad4489e5a3c77cae3dbf97e68ed97dc99c09afc is not running
Error response from daemon: Cannot kill container: 452752e546c1: Container 452752e546c173de98780ac366482e5176c431f393a45a9fa9d46704961aa9ef is not running
Error response from daemon: Cannot kill container: 31eb52e3662e: Container 31eb52e3662ef4544a8482cb620a6b27121c4fec8ac330fa2a9a6c6407761172 is not running
Error response from daemon: Cannot kill container: 048f758b042f: Container 048f758b042faabd08bc2fa91b4a3a02bf146f794270933f52117375992b3bdc is not running
Error response from daemon: Cannot kill container: 28ca19f34b18: Container 28ca19f34b18461375349d917c95329c46da46f4d0c025e6454fcf090187a379 is not running
Error response from daemon: Cannot kill container: eb6e58ba385d: Container eb6e58ba385db46e9a825dc486356c3197b36447c2b7cadf0a6af71a7dbd4969 is not running
Error response from daemon: Cannot kill container: 43ac3af5a730: Container 43ac3af5a730c920872ec9d4ae87e9360b082bf94d3745c0c811f608ed7ef44c is not running
Error response from daemon: Cannot kill container: 8834e513828f: Container 8834e513828f1698b2206d6d144c8f555ba4733b8b41b9000bb54062efc6c94b is not running
Error response from daemon: Cannot kill container: f5d532a8d70e: Container f5d532a8d70e53ebe88197ddca37dbf549aace2aadbde0c2a0cd5e136ad8dcc5 is not running
Error response from daemon: Cannot kill container: 0fa61acb8764: Container 0fa61acb87642b88d919bce4a35c52a553740ee4a188c283edf709d0770ec76e is not running
Error response from daemon: Cannot kill container: 1af8b26bdc5f: Container 1af8b26bdc5fb6f98eee28fb3df5dece466925c3f7ccbebef34684da28b58591 is not running
Error response from daemon: Cannot kill container: f65826dcc8ca: Container f65826dcc8cade4dea5e5da93a3686a8d6d522ced56875eb6ce7cb8632e38fc6 is not running
Error response from daemon: Cannot kill container: 6d01eb975cc9: Container 6d01eb975cc9ffabbde073870dee722a926648b53306acffd852de352c46727a is not running
Error response from daemon: Cannot kill container: dd4b9598d1cf: Container dd4b9598d1cf83a30198e358a6578cc8792afeedc8b654e97414c70eef185511 is not running
Error response from daemon: Cannot kill container: 418deff0d523: Container 418deff0d523ca5c716d33c98207c969e20ad85fe6a5247205877d42f6db0429 is not running
Error response from daemon: Cannot kill container: 3aa59a97b66b: Container 3aa59a97b66bda984e09b587d1ee81c9720e20db0ce18ab4ada1e38f43872788 is not running
Error response from daemon: Cannot kill container: 971260ceab6a: Container 971260ceab6af9c550514c2117f48a78a997052e55885fd4497f1e930fdb2c83 is not running