GUI acceptance tests using environment deployed from packages.

Build: #2027 failed

Job: Onezone spaces multiuser was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
16 minutes
Revision
06b7ddbe39e2302126bded895dfde2e9f3fa8004
Total tests
13
Successful since
#1943 ()

Tests

  • 13 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  49500      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: 415d7f9e7ad1: Container 415d7f9e7ad1cdaf9318d17a8d79206ff60b7397a9749e8b598271ed76570723 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-COSMT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/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-COSMT/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-COSMT/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-COSMT/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
W0317 07:51:16.988452     441 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  39100      0 --:--:-- --:--:-- --:--:-- 39100
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 448fddb2c575: Container 448fddb2c575a3cd241728f61e34517b0781f3a5f66fa6f8c6f743588df6f0a8 is not running
Error response from daemon: Cannot kill container: 3db678089b60: Container 3db678089b602b7abf3e2b560854c25d34d9594d5bcace3c1434235e21b420e1 is not running
Error response from daemon: Cannot kill container: 7fc7e472f1c9: Container 7fc7e472f1c98b13a741cbb2e3930f7f29ac6d6e06cdbf81cc529c455350ed3b is not running
Error response from daemon: Cannot kill container: e489730cd9d4: Container e489730cd9d42cc5ffcbad405c48a35bf097de7f5633d14dea362da930c57721 is not running
Error response from daemon: Cannot kill container: d7bd11fc6da2: Container d7bd11fc6da20f8ae95cd479f84c72f58c7fa4f1b4d25e6f6a3c7f00f334a72a is not running
Error response from daemon: Cannot kill container: 029513486a7e: Container 029513486a7e17b3834d6999550e9164744d4cd09c0bc5af942ec191cfd17153 is not running
Error response from daemon: Cannot kill container: 231cc5a84d34: Container 231cc5a84d34f801a7588b3f3d86f2c1ce83a98a613ab2ba8a734c200d8f09d7 is not running
Error response from daemon: Cannot kill container: 3c89b392378d: Container 3c89b392378d42711b2537eb04cd7a0e272e05ad6dac557410e1a50634b2ee15 is not running
Error response from daemon: Cannot kill container: c29687f92677: Container c29687f9267710426a36fc57b44de5eae7dc0c33d83b5194b2f7a7872436b030 is not running
Error response from daemon: Cannot kill container: a4d169a0e09e: Container a4d169a0e09ebb0a5c18a52e8a58b8dbe14a7913f89f3e1f63695597e8538f19 is not running
Error response from daemon: Cannot kill container: d5a5ca142529: Container d5a5ca1425290aa7c8f7ffb9797593e1fbb1bba7084f1a2f7c1e14bbdb19617f is not running
Error response from daemon: Cannot kill container: abc6d00ede94: Container abc6d00ede941da8b9d0023088afa734ff5b938dbf32e38ba28a13f7ce5b17fe is not running
Error response from daemon: Cannot kill container: 17510048fe98: Container 17510048fe980256d606e89ccec522ce9b783f686e4ff2230ff0f88a36668fee is not running
Error response from daemon: Cannot kill container: 37d1eb719869: Container 37d1eb719869dbbea4ab406c7948a3d8a08b1326354e2c4bbd3ee7bdd735f921 is not running
Error response from daemon: Cannot kill container: eaea3fdc99a9: Container eaea3fdc99a9597db04cf505295ec9d47db9dd2498aba2b32867cc093378787c is not running
Error response from daemon: Cannot kill container: 3aeff0e33568: Container 3aeff0e33568c9fe30b68bd1250050fc72491a0cc927f5aae36dcce31e70d78a is not running