GUI acceptance tests using environment deployed from packages.

Build: #2149 failed

Job: Oneprovider ACL files metadata was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
16 minutes
Revision
55cdb7fe92fff892fdb8cf16f00c4ce6627a4c4a
Total tests
10
Successful since
#2109 ()

Tests

  • 10 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  49500      0 --:--:-- --:--:-- --:--:-- 49500
Error response from daemon: Cannot kill container: f6d36a90fd02: Container f6d36a90fd0294da4f71b0bdc1f2f96fbd25fb06afc297bfc6e9259725514bab 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-COAFM2/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAFM2/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAFM2/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAFM2/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAFM2/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAFM2/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-COAFM2/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-COAFM2/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-COAFM2/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
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
W0525 21:14:23.369266     440 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  48978      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: b3f5c6d2a8a7: Container b3f5c6d2a8a7a274524618085c49855686fb9f6f85702b4037ff3679eddea43e is not running
Error response from daemon: Cannot kill container: 4a586052d62b: Container 4a586052d62b32bc2900ce999868621e9db5f072a9c964f8b6b9d75f7908f8a0 is not running
Error response from daemon: Cannot kill container: 7c2502134781: Container 7c2502134781d4d7add32f456b4304ff090f54d68553a61486c122416e34d92c is not running
Error response from daemon: Cannot kill container: fb9fc5e6001b: Container fb9fc5e6001b7c82c055259d68785c7fd8ddbdda5af0fefe17fe63c531499f7c is not running
Error response from daemon: Cannot kill container: 40d9a92cf518: Container 40d9a92cf518d6f5b79b33f91ccb48aaae960ddce1c2abd42446595880a27f10 is not running
Error response from daemon: Cannot kill container: 20ca95ed4964: Container 20ca95ed4964087ea4f15e51a6dddd48d0062eea7afab0c589829803778e73b8 is not running
Error response from daemon: Cannot kill container: 671e160110e8: Container 671e160110e8ae963ca06fd6ca3ea0250aaf320932a6fc56d06c422ac73286f7 is not running
Error response from daemon: Cannot kill container: d47621c16187: Container d47621c16187adeb88847c771812c9d62918c769dbece951d41d325e50f79933 is not running
Error response from daemon: Cannot kill container: 922131d96e70: Container 922131d96e70060263a46a6761746466cab802189bffefad3b05161618e82bda is not running
Error response from daemon: Cannot kill container: ab669912d598: Container ab669912d5980daa65c2c893e240f5e04752fa72fab89eb6a959c40833fb7958 is not running
Error response from daemon: Cannot kill container: 33c88ceeb1fe: Container 33c88ceeb1fe41b71402cf0fcf3f8907039fb5738f17426a60c1a6f888164be8 is not running
Error response from daemon: Cannot kill container: 0f1d7f1b9a48: Container 0f1d7f1b9a4868748484bbf821c67731f54bf25ad25066b134fc2a616a691cf5 is not running
Error response from daemon: Cannot kill container: 579704c1bf7d: Container 579704c1bf7d165e3383640fc4f5776f55be73e8723adad60cba96c125a50227 is not running
Error response from daemon: Cannot kill container: ed3f54c10b0d: Container ed3f54c10b0dbad428c64b042cb418f32e8501c2b97a7adb7d7219fa58b80fe8 is not running
Error response from daemon: Cannot kill container: a501c63ecc32: Container a501c63ecc32af65fa19c83079f97f1c6a145776d37b5c026d1c648b17304c29 is not running
Error response from daemon: Cannot kill container: e938bf704025: Container e938bf704025acbdaf6235a0823f5f7f98c2629c4119f1366b54c45e8b410707 is not running