GUI acceptance tests using environment deployed from packages.

Build: #2150 failed

Job: Oneprovider data tab was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
16 minutes
Revision
55cdb7fe92fff892fdb8cf16f00c4ce6627a4c4a
Total tests
28
Successful since
#1943 ()

Tests

  • 28 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: 0e1a42a7a202: Container 0e1a42a7a202984a39dc8e46006ae4f757cd7b6a381f9dee57823d34e22abbbc 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-CODTT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODTT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODTT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODTT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODTT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODTT/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-CODTT/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-CODTT/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-CODTT/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
W0526 20:34:28.664800     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  47969      0 --:--:-- --:--:-- --:--:-- 47969
Error response from daemon: Cannot kill container: 85d3dccda966: Container 85d3dccda9663842050f5a78706c2985d54e91daf61c7ace2d3ba8a53be9df6a is not running
Error response from daemon: Cannot kill container: 4a682b62aa16: Container 4a682b62aa162d88f87e1748731a476957e3c3fe5f79f0cc7a06a0b06fa9fbc1 is not running
Error response from daemon: Cannot kill container: 5b5a8a0f8952: Container 5b5a8a0f8952f853a7219f87964620c13643793e0dfb0a571f7da2f40eb6561e is not running
Error response from daemon: Cannot kill container: 5af863024942: Container 5af86302494261c8617753bb961b6624031d574de50267240e73b2a00160b583 is not running
Error response from daemon: Cannot kill container: 79749acfeb1e: Container 79749acfeb1e1bbd80428ce9caebd74ba5585edf056beba91a074d94ca26188c is not running
Error response from daemon: Cannot kill container: a8d5a51a0836: Container a8d5a51a08362911fcb28e2898dafe147a9a6f8d3a511c04494090bd894076fb is not running
Error response from daemon: Cannot kill container: 0610e6fc627e: Container 0610e6fc627e2f6648fe800281cf79a4dcb3371eae631abc7b885d0e550535ed is not running
Error response from daemon: Cannot kill container: 9b414f4665fe: Container 9b414f4665fe8a811728c9289cb7ac281ad92e8c69b583ef28b985164b519dee is not running
Error response from daemon: Cannot kill container: 6c557c9dcb3a: Container 6c557c9dcb3aabac441ae5d1ab8719e5bf9006769905e8d4e33dd61e930f21d5 is not running
Error response from daemon: Cannot kill container: 4befacfea9b8: Container 4befacfea9b804206fed5e304f8f06a59348786f49f0385b7f5ec9626cc20747 is not running
Error response from daemon: Cannot kill container: 34c3b537af4d: Container 34c3b537af4d39ac7757a7a8fc19406c266edbdbe0366e7a8fc9eeb67e5c83a9 is not running
Error response from daemon: Cannot kill container: af10db51e398: Container af10db51e398e8ab04d09df9e6883bec6f39aa4a5f806163f9dda9a6b9cf266a is not running
Error response from daemon: Cannot kill container: 2c88d6475bef: Container 2c88d6475bef28b472e5744d9c8c579df298ff61122690b018e258cf3e4ccdba is not running
Error response from daemon: Cannot kill container: 532130716f90: Container 532130716f9042c2dd0d0fbcd77f290072fe3091cf6986d2fe667bf4c4025165 is not running
Error response from daemon: Cannot kill container: 807ebe4ed4a2: Container 807ebe4ed4a29cd3ca0b48b0898a538420fa05954b08446877a30c8bbd10b0e6 is not running
Error response from daemon: Cannot kill container: 117c3310c0ab: Container 117c3310c0ab1ab347e533c92ed84e911accc2fe4624c1e06d25c4c8112546d1 is not running