GUI acceptance tests using environment deployed from packages.

Build: #2216 failed

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
38 minutes
Revision
6fbe1bf8d7f1e016c40c256738227d3e7e51aa7b
Total tests
17
Successful since
#2201 ()

Tests

  • 17 tests in total
  • 37 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  45617      0 --:--:-- --:--:-- --:--:-- 45174
Error response from daemon: Cannot kill container: 0d3ab98c8e09: Container 0d3ab98c8e09d16e5845b9bc22efdd4911e6a2bb9b6e6899118f142b6a9c8a9f 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-07-09 20:39:11,858 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-07-09 20:39:11,858 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-07-09 20:39:11,858 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-07-09 20:39:11,858 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-07-09 20:39:11,858 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-07-09 20:39:11,858 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-07-09 20:39:11,858 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-07-09 20:39:11,858 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-07-09 20:39:11,858 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-07-09 20:39:11,858 WARNING Connection pool is full, discarding connection: 127.0.0.1
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]
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]
W0709 20:53:58.880375     452 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  40815      0 --:--:-- --:--:-- --:--:-- 40815
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 7eabd61dfcc2: Container 7eabd61dfcc2416361c27857655c8b323c5501750f2d8a9058540eca2fd60f3b is not running
Error response from daemon: Cannot kill container: b10678344f9c: Container b10678344f9c421ed35a81974bc8defbfce2d4ca2dc88e5f9605604644890335 is not running
Error response from daemon: Cannot kill container: 39a02f795127: Container 39a02f79512757efd01e126e638b29dda7e1fc14d3a34a8712e11b00ea61982a is not running
Error response from daemon: Cannot kill container: 10c2be4fde3b: Container 10c2be4fde3b21600ac81f522ae17bc8466412af143293113e02a17f66992dbe is not running
Error response from daemon: Cannot kill container: 378b4b04742b: Container 378b4b04742b94ba33b3958889524e9c9080f5c920345230ef3a6482ab02ea1f is not running
Error response from daemon: Cannot kill container: 975a4a6b36f2: Container 975a4a6b36f28d667d542cce80ec4c1f271f286ab1fe393121e7914aa21ed199 is not running
Error response from daemon: Cannot kill container: 3b6adce5c76b: Container 3b6adce5c76b1e34ed195ae9c3bedc3bf3002daf936e3becb375e73362624aca is not running
Error response from daemon: Cannot kill container: 14e95d23d0e7: Container 14e95d23d0e7c2c525e7725ec766dfc778faf538b75c434a151427bdb43d58d3 is not running
Error response from daemon: Cannot kill container: 6f3a6140bd8d: Container 6f3a6140bd8d53c86cd5102398f2fb5006ff33c2d4e3ba05c52d1f0f8447c32e is not running
Error response from daemon: Cannot kill container: 04c6b07b4ec3: Container 04c6b07b4ec3c4df4532483871b7499b4f337081ccdbaeeea512cff26d93c391 is not running
Error response from daemon: Cannot kill container: 061ca55cb4c5: Container 061ca55cb4c525ab5ad63eaa7e20827ee4e07eb5e643a3a5dd3ee95af8270e9f is not running
Error response from daemon: Cannot kill container: c46c81b09845: Container c46c81b09845d725858efc6648f18e76080cefb4fe1a05f1d673dcba89ee3f5f is not running
Error response from daemon: Cannot kill container: c2bda244188b: Container c2bda244188bf87f6b85889109ee8b80855bb3396cffc9367fe092c96ff4f581 is not running
Error response from daemon: Cannot kill container: e84093936f29: Container e84093936f29641c99cfd9e77076a65cd746b1af7b7dd18ca6266867e6e30827 is not running
Error response from daemon: Cannot kill container: 735ec85d12e3: Container 735ec85d12e3fd0016aef5cb45e4173bdb17bfd22e9fbe80b64354ebe44ec97c is not running
Error response from daemon: Cannot kill container: d778dd47290c: Container d778dd47290c932b506d24f820764daa7c109f7b9fb699f07ffb33474d285407 is not running