GUI acceptance tests using environment deployed from packages.

Build: #2041 failed

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
39 minutes
Revision
ede44e43ac4719043bc240bfa18cbbd42526087c
Total tests
17
Successful since
#1943 ()

Tests

  • 17 tests in total
  • 38 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  18105      0 --:--:-- --:--:-- --:--:-- 18105
Error response from daemon: Cannot kill container: 5dd2bdf70244: Container 5dd2bdf70244a345b1ed3f546c6657b3d4b9a95615f59b22de1064cba16b2cf6 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-CODDT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/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-CODDT/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-CODDT/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-CODDT/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Unable to find image 'onedata/acceptance_gui:v8' locally
v8: Pulling from onedata/acceptance_gui
a1298f4ce990: Already exists
04a3282d9c4b: Already exists
9b0d3db6dc03: Already exists
8269c605f3f1: Already exists
c810ae7364ef: Already exists
78d356e6ec21: Already exists
792b20546d07: Already exists
c1d3130a77b3: Already exists
0c7ad6b015da: Already exists
114ec36e4007: Already exists
2bc588dde0c7: Already exists
89641d7ca7e2: Already exists
b6cd4b44aa19: Already exists
e1c77802a505: Already exists
f373aa611054: Already exists
Digest: sha256:97e4de524ef380ad8c07bf6c71280c378a5e0179834942ff0e6c0007d32b148c
Status: Downloaded newer image for onedata/acceptance_gui:v8
Error: could not find tiller
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
2022-03-19 20:18:20,942 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-19 20:18:20,942 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-19 20:18:20,942 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-19 20:18:20,942 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-19 20:18:20,942 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-19 20:18:20,942 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-19 20:18:20,942 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-19 20:18:20,942 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-19 20:18:20,942 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-19 20:18:20,942 WARNING Connection pool is full, discarding connection: 127.0.0.1
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
W0319 20:33:38.420636     435 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  22808      0 --:--:-- --:--:-- --:--:-- 22921
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: e92d69a08c26: Container e92d69a08c2624a9e3ce3c7b834f29db11e70818427ee1583c808da4d878cf82 is not running
Error response from daemon: Cannot kill container: 3ce73baa3eec: Container 3ce73baa3eecd933ab7d5ad79ca300836bb2635b7d773b7a04980d989401f87a is not running
Error response from daemon: Cannot kill container: ae8f543d2e56: Container ae8f543d2e56cfb81df2857512905580628c3d87adc3c8ecdc2de990659b9135 is not running
Error response from daemon: Cannot kill container: bfd0223ea396: Container bfd0223ea3964d543713bd4757ae15dde6c84a34647a34938c942df09a3c6da5 is not running
Error response from daemon: Cannot kill container: 45e2fff9e45e: Container 45e2fff9e45ed838a1124b287815d25d0ed342ab93fed3c35db5c6077c257e3f is not running
Error response from daemon: Cannot kill container: 3ef6145d6b1f: Container 3ef6145d6b1fb2184cb58017bf62fb62f32496277c6d1d6e689fe6c2509cf5de is not running
Error response from daemon: Cannot kill container: fc51e6f46ed5: Container fc51e6f46ed51e29dd59653df0a2069422b12b59bf52aa300f37f3648f9d51a1 is not running
Error response from daemon: Cannot kill container: cee98b9cb66e: Container cee98b9cb66e96b9c2c596a8229a7459d019245bf04fbf17418fa4815ddf54e2 is not running
Error response from daemon: Cannot kill container: 3ffd56d07169: Container 3ffd56d07169837d0d07ad1af407fddb02d8ecf17f869f0684ff804d9881de6b is not running
Error response from daemon: Cannot kill container: cbdf28c38be2: Container cbdf28c38be282c2fb56a502853164edcc2e08aa62da3ff9fdcf81c1f684fb3b is not running
Error response from daemon: Cannot kill container: 97d9439484a2: Container 97d9439484a25018aa096bcfe4eb2ffff8b9b4585d54cfbab7e901f649080c64 is not running
Error response from daemon: Cannot kill container: 0a97a2a6504e: Container 0a97a2a6504ef2724caae16aab37c3a7d2b1035b8fdca660a0502ff283dbab44 is not running
Error response from daemon: Cannot kill container: 972ed36e30c5: Container 972ed36e30c5c36b27e5abf991758ca44c4bd8be2de4c63213887b36051e3488 is not running
Error response from daemon: Cannot kill container: afa461341f32: Container afa461341f32a306ec890db1bd5546fc3ca9e3199ac5e26668ffe116a28299fd is not running
Error response from daemon: Cannot kill container: 6b2867dafe02: Container 6b2867dafe02e5814e3b3dae9e70cc76cb2398f0d4800724b809618b2340f44b is not running
Error response from daemon: Cannot kill container: 3187a0c0c9cc: Container 3187a0c0c9ccbc5fc4df396d12bbbb9178e62619b737e88384597ef94db184c1 is not running