GUI acceptance tests using environment deployed from packages.

Build: #2150 failed

Job: Chrome onezone automations tests was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
34 minutes
Revision
55cdb7fe92fff892fdb8cf16f00c4ce6627a4c4a
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
  • 33 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 --:--:-- --:--:-- --:--:-- 50032
Error response from daemon: Cannot kill container: 4d81a9f4d86c: Container 4d81a9f4d86c4539486408cc47c96ef96d2b8e07f22c2766c4f7cbca2fbdc497 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
W0526 20:59:37.868983     436 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  44314      0 --:--:-- --:--:-- --:--:-- 44314
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: a46e2662ff62: Container a46e2662ff62ff042adf8fc118edf7adecb433966293d4ae5c8f2768a4b8413f is not running
Error response from daemon: Cannot kill container: 41a8d2b43a89: Container 41a8d2b43a893e629e6420ab6e2546bbc7349a36b3f2920bb76cacc3a20cd7d3 is not running
Error response from daemon: Cannot kill container: cf42e8ed7395: Container cf42e8ed739577460ce48bd0c717b194511fc9cd28beaa0556dcf85817437ece is not running
Error response from daemon: Cannot kill container: d79c0d87067f: Container d79c0d87067f1408492d3614054a823268ab362791d96d02c0910d3e2e6f7094 is not running
Error response from daemon: Cannot kill container: 5442e55c1324: Container 5442e55c13246b9414135ea18ecad5b2aa54044563046afec0f1dc7eadbc1492 is not running
Error response from daemon: Cannot kill container: 3981c9369f45: Container 3981c9369f45d4340387b55a1baebcf3342b18c5f4840c9ef21b0c160df4b8ce is not running
Error response from daemon: Cannot kill container: db51b7dd1139: Container db51b7dd1139d169a202c5f33fdbb7da815ff783e2d7443a14f4edbee45dd14d is not running
Error response from daemon: Cannot kill container: fe0fbccc4435: Container fe0fbccc443506bf9c79869468b544ed3d07ec339dd8c10149510797bbf74ebf is not running
Error response from daemon: Cannot kill container: 0de032eacf7b: Container 0de032eacf7b8e93ff2ac3d48594b1156c9019b48e17d05c22dc40c163964d0a is not running
Error response from daemon: Cannot kill container: 28aa70d5820d: Container 28aa70d5820de5c0c35697eacfad26faf2810200b1132e67d506ebaa5a3701fe is not running
Error response from daemon: Cannot kill container: a1451b60ba8a: Container a1451b60ba8af2c50d41ee698a29692bc298799211f54a43749871eaa7d2756c is not running
Error response from daemon: Cannot kill container: e8939a97a112: Container e8939a97a1125e20e627009d20f04ce3d7aea5591b874a677cfb2acc2e6c385d is not running
Error response from daemon: Cannot kill container: 3fdeb21bb194: Container 3fdeb21bb194da1b533dd9eba2842ab46fce6043f8522e2eef0e055f96b83302 is not running
Error response from daemon: Cannot kill container: 7be474702cf0: Container 7be474702cf0fd727139ed4613f8a78db8024dfc5b77bbae3deea8f826db33ce is not running
Error response from daemon: Cannot kill container: 336071881c49: Container 336071881c496b9fbc009da3e3b2d4d50af1754cbd706b6820678a2d5727ef32 is not running
Error response from daemon: Cannot kill container: d0e7ec6cd4ae: Container d0e7ec6cd4ae160d7c2cf6ff008e6163845c56e64073d708089d18260ba728f7 is not running