GUI acceptance tests using environment deployed from packages.

Build: #2081 failed

Job: Chrome onezone automations tests was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
35 minutes
Revision
13c8582397a5a6dbba3b40c37b28e380225c1c27
Total tests
37
Successful since
#1998 ()

Configuration changes

Job Chrome onezone automations tests with key ODSRV-GAPT-COZATT no longer exists.

Tests

  • 37 tests in total
  • 34 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 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: 6a1a5797b7c8: Container 6a1a5797b7c889c5ce107b7650666c4eb35b0d914b48b9de4e41911dae6ca28d 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-COZATT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/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-COZATT/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-COZATT/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-COZATT/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
W0405 21:49:34.822844     438 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  39769      0 --:--:-- --:--:-- --:--:-- 39769
Error response from daemon: Cannot kill container: c92a24201733: Container c92a242017332b6c1e7d0dde95457b9f0639d47e2a96adf2dc4698fcea9c1499 is not running
Error response from daemon: Cannot kill container: 08b9b9ed2847: Container 08b9b9ed284731d806637956954914ba13f12376d38d4903fda10e72caaf1832 is not running
Error response from daemon: Cannot kill container: 5a6b81f31556: Container 5a6b81f31556dc5b903e6699bfd1ce1046a94fde19134a87af22f379be5144b9 is not running
Error response from daemon: Cannot kill container: 6c3a4a495d99: Container 6c3a4a495d99c35de79feb3485fa57cb9ace0f6bcfda28a636d5053eeca11800 is not running
Error response from daemon: Cannot kill container: 683c7f669846: Container 683c7f669846c9319e9eb7c98c24eb753f679f370edf4851c8517241a876b328 is not running
Error response from daemon: Cannot kill container: 92b51007213f: Container 92b51007213fb9961ae9ecbcf8f7040809149097bb85258d4f0b518e92945ab9 is not running
Error response from daemon: Cannot kill container: 9ab9dd1bd3f0: Container 9ab9dd1bd3f0c4bdf664c764b9f0c4ad00c80465ac4fb237d57d3481a06ac280 is not running
Error response from daemon: Cannot kill container: 2f422694997a: Container 2f422694997a0915100b8598c56acb680f4c15f0f33169d9073620829254e8d6 is not running
Error response from daemon: Cannot kill container: ae6aeecbce76: Container ae6aeecbce7685d697cffa90ecf420a05984eccdfef83ec929822b6b2e6bdf84 is not running
Error response from daemon: Cannot kill container: 97dd6189f96a: Container 97dd6189f96aad4d1fcdbfed744bb1aff4f9d81390192e9ee432243423f162d3 is not running
Error response from daemon: Cannot kill container: 5d89686a75d8: Container 5d89686a75d8cb1c8a5beb9f19ab58a4cfbef80c98fb29c61e0bffc70862eccb is not running
Error response from daemon: Cannot kill container: f98e082e8c32: Container f98e082e8c32b1315a17d00c7d2a92a3b52970a88237c4a3bbb2c265299714a9 is not running
Error response from daemon: Cannot kill container: 5336fb803cb2: Container 5336fb803cb26522125f4fef5b7d2418b953fee82e6e438f2375c727644f51af is not running
Error response from daemon: Cannot kill container: 0078a19245bb: Container 0078a19245bbccb5a3040152a05aabe9d9293b08fc82779ddb1bfddfa3cc5aa9 is not running
Error response from daemon: Cannot kill container: b1b141e258fa: Container b1b141e258fa443a317ffbefb5e9aa05ccb4ccbb71bde99e88450820d445612f is not running
Error response from daemon: Cannot kill container: cac48c9a5be3: Container cac48c9a5be3381591a241c9c6ca303356fbd847653680e0854c222cac6428b0 is not running