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

Build: #2488 was successful

Job: Access tokens was successful

Job result summary

Completed
Duration
13 minutes
Revision
8bf7c9f6df4b77754518d5d91f1bda1a458ce27e
Total tests
2
First to pass since
#2487 (Child of ODSRV-OZP-1780)

Tests

  • 2 tests in total
  • 10 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  17169      0 --:--:-- --:--:-- --:--:-- 17169
Error response from daemon: Cannot kill container: 61353cb3afac: Container 61353cb3afac93a42bea34a540aebc216faad45c8ef98c5f878fa9b9e790aa9b 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-CLT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CLT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CLT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CLT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CLT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CLT/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-CLT/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-CLT/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-CLT/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: could not find tiller
groupadd: group 'luma_group' already exists
useradd: user 's_user1' already exists
useradd: user 's_user2' already exists
useradd: user 's_user3' 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
id: ‘user3’: no such user
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
id: ‘user3’: no such user
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)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Defaulted container "oneclient" out of: oneclient, wait-for-onezone (init), wait-for-token-dispenser (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
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  36637      0 --:--:-- --:--:-- --:--:-- 36928
Error response from daemon: Cannot kill container: d17844c48318: Container d17844c483186b33323b1b2ff694f690a5467b64b2d99faee4ad6d4a61ee5ad4 is not running
Error response from daemon: Cannot kill container: d4aa9c2735ee: Container d4aa9c2735ee034836a2f97021ba6b6c2ec8495855d8247ab7e720bad1f49f09 is not running
Error response from daemon: Cannot kill container: 9d5b3dc64a42: Container 9d5b3dc64a42e95aa98f074b39f0d52d1cbec797d7fcb9270e8518cdf212a6cd is not running
Error response from daemon: Cannot kill container: 943f2b75922a: Container 943f2b75922a7b1b609e6ab5fc6b99f762bedaf68028abcd51f5ec8fa967d861 is not running
Error response from daemon: Cannot kill container: d2c1d81c92ef: Container d2c1d81c92ef51d158b349d0567a8af1c0b2d617147c0b52f5baaf44c7a62415 is not running
Error response from daemon: Cannot kill container: 2b13511a609f: Container 2b13511a609f5a94c68155ee0d891d995cdb5fbc9fd251180eea9a7e9cbfd20e is not running
Error response from daemon: Cannot kill container: d5a55d890cf7: Container d5a55d890cf773318d867e4e842ed828edd1e5b606edfdc35c1d20183d422003 is not running
Error response from daemon: Cannot kill container: 275611a961ef: Container 275611a961ef79696423b262cb1b9bba48a2809e2cd60e2f1bb44699498ad140 is not running
Error response from daemon: Cannot kill container: 7fe792f181c3: Container 7fe792f181c3ed86fc176d7367b26ce8ce88da23ef2b58d2b2ac754db9031bdf is not running
Error response from daemon: Cannot kill container: fcdebefa54ee: Container fcdebefa54ee52134a0ad028de6ac32a8893b1ad086ff0e7e3257d242df94021 is not running
Error response from daemon: Cannot kill container: bf98a0084a1b: Container bf98a0084a1bd67c56a311030e1987a127c6bbdb4b8997ebd8ba960dff37dead is not running
Error response from daemon: Cannot kill container: f9521d164bf4: Container f9521d164bf4a3236572e9c60b3daf5d39158b61dbc65376b5b941f2b4d08568 is not running
Error response from daemon: Cannot kill container: 6ddc3f304da0: Container 6ddc3f304da06272635c699f8a5bd41d67f7b5c6bf1a40946f1be89692f54e63 is not running
Error response from daemon: Cannot kill container: e408b3399043: Container e408b3399043dbf99e47f788da17e937deba78b6b42b69206fc95600e7b34bdb is not running
Error response from daemon: Cannot kill container: 30a730dd299c: Container 30a730dd299ca6870b8d94b13799938dd1c0dac85c92a4a2cb5cb64fab769348 is not running
Error response from daemon: Cannot kill container: 26beaa444a60: Container 26beaa444a60e143a1917f2d0add9c71ff4a2fa3c2e7c3480b67819f8a2286f6 is not running
Error response from daemon: Cannot kill container: d4dd26e01557: Container d4dd26e015575da3d3b6280bb3a01c9724e9be2f20bd6706afa4d1641a4263ab is not running