GUI acceptance tests using environment deployed from packages.

Build: #2118 was successful

Job: Onepanel members was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
24 minutes
Revision
531283e2b89b3833269b775ff1b3609165404e1a
Total tests
14
Successful since
#2109 ()

Tests

  • 14 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  47000      0 --:--:-- --:--:-- --:--:-- 47000
Error response from daemon: Cannot kill container: 10617d15f1e2: Container 10617d15f1e2de9003a69ec1e2756f7e5dad9091d86696185af4308c5d36225f 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-COMT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COMT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COMT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COMT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COMT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COMT/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-COMT/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-COMT/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-COMT/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
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]
W0422 13:22:27.384273     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  45174      0 --:--:-- --:--:-- --:--:-- 45174
Error response from daemon: Cannot kill container: e5b2f23b9946: Container e5b2f23b99460a65f93d761deb08ecd148b5ae4eaad9d072751d7a9e5a056148 is not running
Error response from daemon: Cannot kill container: 994397b9952b: Container 994397b9952b31ee144d6e340b5793eef744b1239972d3bc542273d1dc975fd5 is not running
Error response from daemon: Cannot kill container: b68801308e60: Container b68801308e60dceabd9cbbca5279788078dc7b6939d40cd6c69f870ce49662eb is not running
Error response from daemon: Cannot kill container: 89789681c711: Container 89789681c711f2b2d2cc8e0065bd884d1c867cf5a6e66d128fd6a2d4c0fdff62 is not running
Error response from daemon: Cannot kill container: 1a7a5869fb06: Container 1a7a5869fb06236fbdab30d735122ad95aa1492a3176d364284928c65bc218b7 is not running
Error response from daemon: Cannot kill container: ae15a56c931d: Container ae15a56c931d874d7c0c3b0cac9e40d083cb979765fed302bb7af535b9c62dc2 is not running
Error response from daemon: Cannot kill container: 8b060ce9ddbd: Container 8b060ce9ddbddf7bb0b7aa8b09304a04f657592f43cd7c5600c7081e0840b012 is not running
Error response from daemon: Cannot kill container: 867e6fb97d5e: Container 867e6fb97d5e523a4535d5dcd0c2a610fb028d740dc62bbf12eb1f8f35f244d1 is not running
Error response from daemon: Cannot kill container: 2c8baec1f9f5: Container 2c8baec1f9f554df264d5a1a3ef7201755177e60df5059b3e8cea98c468223f0 is not running
Error response from daemon: Cannot kill container: 9ab5056cd022: Container 9ab5056cd022024c6519415e7a5afda68c4b4b87795371b209da444869b7d70e is not running
Error response from daemon: Cannot kill container: 9e0463d4f429: Container 9e0463d4f429645d2c39bef00ddde90e2fa530f8c79b5e9c9c5e7f29542102c1 is not running
Error response from daemon: Cannot kill container: 0da6ec94a95e: Container 0da6ec94a95e84bec3c027a81b9d585b1990140290528b1fe98d534a1054b44d is not running
Error response from daemon: Cannot kill container: 2d268b159a8f: Container 2d268b159a8fc0a81e9950964172d4c8fc10a822f0ed6c3760d34f04ea52442c is not running
Error response from daemon: Cannot kill container: 439b9230f467: Container 439b9230f4673d86c97dc381bf275aed60e8e8352f2dd78d16553582d9dc205b is not running
Error response from daemon: Cannot kill container: bc1a8ce4875e: Container bc1a8ce4875e16a426d137bfffe2b9c98301fc56fd3b32177661dc55945fb221 is not running
Error response from daemon: Cannot kill container: d060bccd9763: Container d060bccd97631d1fa2e0012c1d1db6547485b1f8f284fcfbf0ce48e8311fa7c3 is not running