GUI acceptance tests using environment deployed from packages.

Build: #2068 failed

Job: Chrome onezone automations tests was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
34 minutes
Revision
46f0bbcd2738e0f530a00e509bab1d1d7bf6dda0
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  41918      0 --:--:-- --:--:-- --:--:-- 41918
Error response from daemon: Cannot kill container: 4c6217e673a3: Container 4c6217e673a386610179b7b61f36625027e96b8948306cf8ee6c40a790d1c3c4 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
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]
protocol version mismatch -- is your shell clean?command terminated with exit code 126

(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
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
W0401 22:01:40.817744     442 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  41176      0 --:--:-- --:--:-- --:--:-- 41544
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 0b052f79703b: Container 0b052f79703b2c762b652887cdb67d96cd3d576feaef09eb7546eb594bfc19b7 is not running
Error response from daemon: Cannot kill container: 954e30601153: Container 954e3060115326e15da652dff25685934a3c6e0c55a474d77d1bf3d39cd4c7fd is not running
Error response from daemon: Cannot kill container: 11499e9c0908: Container 11499e9c0908fd1202ae83ce34fbf80d483a473fd33a1be811ab5d4b1e9d16c0 is not running
Error response from daemon: Cannot kill container: a421573b7866: Container a421573b7866710e13694fb92dcb8631de2b416528aa0f59bdf5ff89dff22e57 is not running
Error response from daemon: Cannot kill container: 7a29a4ffac73: Container 7a29a4ffac739878b602b1f8dbce7ab040a0ce0fe8ccc0cddc395d03c527d49d is not running
Error response from daemon: Cannot kill container: 685311f01d59: Container 685311f01d598ca0f0a6ed9e92c4a94c94b6a3e501ab4975e50087eb17a9feab is not running
Error response from daemon: Cannot kill container: 188753fafb51: Container 188753fafb515ee6e80311927cce5be88aa24bd87d7638bbd1af5974f655f63c is not running
Error response from daemon: Cannot kill container: ae6fba1491cc: Container ae6fba1491cc49ef776233abd0a7523b80a8f2f6f1275f8ecca324ce5b005366 is not running
Error response from daemon: Cannot kill container: 8bff996e2198: Container 8bff996e2198b84bdc05393d043f0fa553fe48395d6a3361590724e782095097 is not running
Error response from daemon: Cannot kill container: 00792381a4d1: Container 00792381a4d102c9b4c302b9c5c621dce6992ec6755b40cfb118cc6ad14c5942 is not running
Error response from daemon: Cannot kill container: be76537d2ab3: Container be76537d2ab34f8cc6ee15d99ee40ed4828dc14e986d03307a3f66af59e7853d is not running
Error response from daemon: Cannot kill container: 1bac7145d27f: Container 1bac7145d27f6633a856032d7b92673c30ff73fec2712e2ad1313e1be8431ea4 is not running
Error response from daemon: Cannot kill container: fdbe4b97c1e3: Container fdbe4b97c1e3c1886233915d55e6697e45a7ecf746d39f21ba34fd48529580b8 is not running
Error response from daemon: Cannot kill container: cb2a69167642: Container cb2a69167642b5f07f47260ad88459dcd6d1e5335544bdc530dc8636c07b4832 is not running
Error response from daemon: Cannot kill container: f6ea545b5bf4: Container f6ea545b5bf4dce87611bb48b247a7242711961d3e21983a80d4b5cb7563f6e6 is not running
Error response from daemon: Cannot kill container: 4e6ace18983e: Container 4e6ace18983e8a66a5627dbf1e3a016f200c3ee4859d7c50c3bb31bd7c8de367 is not running