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

Build: #2462 was successful

Job: ACL two entries was successful

Job result summary

Completed
Duration
23 minutes
Revision
a2577ad5c8df19d48e961bdf05ea5f1feaec71b7
Total tests
24
First to pass since
#2460 (Changes by Michał Stanisz)

Tests

  • 24 tests in total
  • 22 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  48468      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: 23c6c317b13c: Container 23c6c317b13cffebfa422d517fcf1fbab16ec503ccf4b21595eb0e933d0941b9 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-CATE/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATE/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATE/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATE/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATE/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATE/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-CATE/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-CATE/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-CATE/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)
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]
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  43485      0 --:--:-- --:--:-- --:--:-- 43485
Error response from daemon: Cannot kill container: 9041ef7718b7: Container 9041ef7718b77429c5b846365062006ddb3f6b144e45993dc69f38e35bf9523a is not running
Error response from daemon: Cannot kill container: 8d4de9a28406: Container 8d4de9a28406cf10a43eff295f31bbfc1de0995d8986a5a7bdb676a404baeedf is not running
Error response from daemon: Cannot kill container: ab8480a442b0: Container ab8480a442b03dc7a8fd2290fbc9fa19ebafe439017cc5d109e95f8973c67b32 is not running
Error response from daemon: Cannot kill container: e6c76335b8f2: Container e6c76335b8f245ac93603e979fc55c3106471e98391153b65168226288e34f27 is not running
Error response from daemon: Cannot kill container: bf368c3a6a7d: Container bf368c3a6a7df999f20a848f1d919e97911d73b00952ac845483fc23390f5170 is not running
Error response from daemon: Cannot kill container: 77b5823046ea: Container 77b5823046ea812e880fc0d514a80a438424a668a0b6475c8a00d8df1f87c1df is not running
Error response from daemon: Cannot kill container: d27b1e3cce22: Container d27b1e3cce224c289191085950d485b0b92b3b7ae08bb986e84dba8dcfe1165d is not running
Error response from daemon: Cannot kill container: 6044bfc08254: Container 6044bfc082542777253e24cdfbc3e77dd8cc4a828d413ed3c0971894f5fec6d5 is not running
Error response from daemon: Cannot kill container: fa797a007be7: Container fa797a007be7dca990c7040c57805832c485b90c9592133c47063045d91228be is not running
Error response from daemon: Cannot kill container: 489b0fe4e3c2: Container 489b0fe4e3c2ce20db38839597907e7381c81f5af93e28f337b36b46dd089a6e is not running
Error response from daemon: Cannot kill container: 70d90894bc3a: Container 70d90894bc3a6550884c8a694d45e63a25f19b83374bdedd6de0f0519cc849c1 is not running
Error response from daemon: Cannot kill container: ab8afac8a764: Container ab8afac8a764e363f30026b2adc59b721b59864c8eb1778fcf895536270b45c6 is not running
Error response from daemon: Cannot kill container: ba2aa3baa3fc: Container ba2aa3baa3fceffcc066d2e2d3284b4dba3cfad75ec376707d8b5b6d430c9bed is not running
Error response from daemon: Cannot kill container: 9cc005606293: Container 9cc005606293508255a79192b2853fe74897d9be34c08a6ccd423327859c3fd2 is not running
Error response from daemon: Cannot kill container: ffa56e7b4efd: Container ffa56e7b4efde99d84ab881361406f2a355465761bd13be1912798a22f157be1 is not running
Error response from daemon: Cannot kill container: 4b0a66bb0d14: Container 4b0a66bb0d14367af7c8f9038839dd0f74333e416d8b3ed635a20384d3553a9c is not running
Error response from daemon: Cannot kill container: f955068165af: Container f955068165af2956b6c67436ebc136072059bc69343507a05e4a6526849db249 is not running