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

Build: #2319 was successful

Job: LUMA was successful

Job result summary

Completed
Duration
54 minutes
Revision
531283e2b89b3833269b775ff1b3609165404e1a
Total tests
26
Successful since
#2160 ()

Tests

  • 26 tests in total
  • 51 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  18175      0 --:--:-- --:--:-- --:--:-- 18105
Error response from daemon: Cannot kill container: e85ac1809294: Container e85ac18092948d7f93edc8e74c49f43fcf630f32e2ca788601abe4790a6885fb 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-CATC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATC/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-CATC/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-CATC/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-CATC/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
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)
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
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (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
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (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
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  32767      0 --:--:-- --:--:-- --:--:-- 32767
Error response from daemon: Cannot kill container: 1a31fe2f89f4: Container 1a31fe2f89f43faa830f5cf5983c2b83c55a35281877f275a7e0dd7e164e4212 is not running
Error response from daemon: Cannot kill container: 48a24a2814b5: Container 48a24a2814b54e15c9d1eb29e30fc35b7752bcab70be43b0d61f90d1c9bc5236 is not running
Error response from daemon: Cannot kill container: 4e4742c70908: Container 4e4742c7090801687d768a09e0356ae13a8f3947d38ea65339a55d44ac096a8e is not running
Error response from daemon: Cannot kill container: 35612a15f342: Container 35612a15f342351353c271acab1d8b2bf04671396ea63a222e04df67861a2c0e is not running
Error response from daemon: Cannot kill container: e1f8557d6510: Container e1f8557d6510173735309cce5052eb2e7b38bd00524b6e82c165df9d0dd2b408 is not running
Error response from daemon: Cannot kill container: 0474d44e1735: Container 0474d44e1735c8bc4d3d3dab7ebc3b2465532cc3685673d3f62d99ce8fa4ae2f is not running
Error response from daemon: Cannot kill container: 98ecb444b518: Container 98ecb444b5181ae4351223e65f70f1c3efddfcb3a031d869732c3d29e13b48ae is not running
Error response from daemon: Cannot kill container: 7ea981018d32: Container 7ea981018d32eedbf585f82135c081c7db78d9f63e356ed5187428f271dc86e8 is not running
Error response from daemon: Cannot kill container: 2a68e83641a1: Container 2a68e83641a1bacd44e51b52beec689df82f77317fab014036bff4433f4ab5cc is not running
Error response from daemon: Cannot kill container: 3b6f3f41cfeb: Container 3b6f3f41cfeb5ad8a7549b10afef16bcaf42bc9c3cdf6048184cce897145a4e6 is not running
Error response from daemon: Cannot kill container: c941c71e0f96: Container c941c71e0f9634fa72b1686d942543b8e70e6177963d836e31e43b1cafe5ab54 is not running
Error response from daemon: Cannot kill container: 3f16f956a478: Container 3f16f956a47839b0dfc8cbd6740b4a85613534ad3250cc7304f6cf2f5e3782a9 is not running
Error response from daemon: Cannot kill container: f4e5efb9564a: Container f4e5efb9564a4ff957bc1bbc81792240161dcd49683151d037d30495bb9f5e2a is not running
Error response from daemon: Cannot kill container: d2e104f0feb7: Container d2e104f0feb78502478cc31e0b7ca51454f2d46698dfe04ffb50a741f62e4012 is not running
Error response from daemon: Cannot kill container: 8e18c6177c75: Container 8e18c6177c75224d561800c9cc3272b289235fbe14deebd068d09fb08bed49cb is not running
Error response from daemon: Cannot kill container: ec4867c4cc7f: Container ec4867c4cc7f1c8d0d86159931481d28b91f4fd020b84bee653a3b8911047c09 is not running
Error response from daemon: Cannot kill container: a3f5599a0c8e: Container a3f5599a0c8ec558f5f4cd91033f6aba1372e79081398e2bc56fbf3dda83a9ca is not running