GUI acceptance tests using environment deployed from packages.

Build: #2164 failed

Job: Onezone invite tokens with caveats was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
10 minutes
Revision
2a6ac951983b0da397726653daa1ebcdbbe74ca8
Total tests
4
Successful since
#1958 ()

Tests

  • 4 tests in total
  • 9 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 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: 74b7b457fffe: Container 74b7b457fffe522225a88e12076941b7e721441d8d1f4d745093b79e0458f5a1 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-GAPT-COITWC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/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-GAPT-COITWC/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-GAPT-COITWC/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-GAPT-COITWC/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error: could not find tiller
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
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
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
W0607 19:52:12.934608     494 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
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  45617      0 --:--:-- --:--:-- --:--:-- 45617
Error response from daemon: Cannot kill container: 116b6d5cf652: Container 116b6d5cf65296ab3babf1fb21ff1c6da3c90dd2cff90eaea0797c535382ed48 is not running
Error response from daemon: Cannot kill container: 58acbc90febe: Container 58acbc90febe21069fb07a7fc8ea537a86209f9fb29d3d0a9119debdf3f3bd75 is not running
Error response from daemon: Cannot kill container: 00a2989af999: Container 00a2989af9992f9a17660f5e3f312129a811884c59e3e9b4edb031fc555936a3 is not running
Error response from daemon: Cannot kill container: 9780468fb481: Container 9780468fb481192f3283f9f61f9499addee51c1c0a1b063422de7068186eccd1 is not running
Error response from daemon: Cannot kill container: 102648ade028: Container 102648ade02855fd91ffc803122dc6cb648a38cdc21ef829a7e585334de4a739 is not running
Error response from daemon: Cannot kill container: a3fe797f0dc3: Container a3fe797f0dc34a79ae703914e9db083c93f90e57565f6746bd7fa4ea71401111 is not running
Error response from daemon: Cannot kill container: 470d60566502: Container 470d60566502bac6c691e9dab6eaed99740cdb22e12dd221f313d8d3819fb703 is not running
Error response from daemon: Cannot kill container: 7f605d9e8afb: Container 7f605d9e8afbbfd0a6f19a81afcd46842b645bd8a33d440834ee4705eab7d1f5 is not running
Error response from daemon: Cannot kill container: 511c805b6af9: Container 511c805b6af9a8193f4cf4bc66ab69108bda160b99b03ac186210fdf0f0373bf is not running
Error response from daemon: Cannot kill container: 5ea1a7a4eb51: Container 5ea1a7a4eb511cd89239ab1e3be69bbd09c980570a66cf758c8593e6f1df8597 is not running
Error response from daemon: Cannot kill container: dc1d1aced358: Container dc1d1aced3582532d98507e2c8b2a08d9d407b0696d6ea1ab17918d1e132abbb is not running
Error response from daemon: Cannot kill container: 8e273284e0d8: Container 8e273284e0d8c966d0db27f4b27801edcd152ff4dc384a144b5f0a6ab20527c8 is not running
Error response from daemon: Cannot kill container: e8d84055e767: Container e8d84055e7672f847c9e38c18640de874ba12328015c6b8cc08773565067aba7 is not running
Error response from daemon: Cannot kill container: f62c488af1c4: Container f62c488af1c4278d049490370cacd928a589608af2dcaef8ef993d4e4f797f22 is not running
Error response from daemon: Cannot kill container: 85561c0f2baf: Container 85561c0f2baf096317ccb7bc021d3f7ac92c7d526c821666a83e1d49f795f51d is not running
Error response from daemon: Cannot kill container: a8646543a234: Container a8646543a2340ee1de444d19d7309b262d6f23aee5ccfb0985e6035beb8a21dd is not running
Error response from daemon: Cannot kill container: 059ae9242a2c: Container 059ae9242a2c3a7bae102c58bbf2a129086fc5286963ca5c2107bccc533b838b is not running
Error response from daemon: Cannot kill container: 113a6b25890e: Container 113a6b25890e71934717d091b705d5c1885738bd66a60b7954674acae7e6ba18 is not running
Error response from daemon: Cannot kill container: c0de8f0ac48e: Container c0de8f0ac48ee280bcb708942793f6660d1cf28c859d67b8452f056dc7379230 is not running
Error response from daemon: Cannot kill container: dae82694fa03: Container dae82694fa039225f73d87c278dbb933be5f1bbb6f6e50668378291928f24447 is not running