GUI acceptance tests using environment deployed from packages.

Build: #2147 failed

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
27 minutes
Revision
55cdb7fe92fff892fdb8cf16f00c4ce6627a4c4a
Total tests
17
Successful since
#2113 ()

Tests

  • 17 tests in total
  • 26 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  47969      0 --:--:-- --:--:-- --:--:-- 47969
Error response from daemon: Cannot kill container: b73c9a2aea19: Container b73c9a2aea19c5c53e35841c44af02fa58eca74930e844817090937c3d99594a 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-05-24 20:58:36,985 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-24 20:58:36,985 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-24 20:58:36,985 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-24 20:58:36,985 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-24 20:58:36,985 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-24 20:58:36,985 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-24 20:58:36,985 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-24 20:58:36,985 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-24 20:58:36,985 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-24 20:58:36,985 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
W0524 21:09:07.137003     447 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 from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 4f94bc4036e7: Container 4f94bc4036e77f42ea2e04103f01cd3f790272d4af3d1da194c2691c3e69f9f1 is not running
Error response from daemon: Cannot kill container: a231d57a9e8c: Container a231d57a9e8ce331b469c2abcfb233b6ba6c0c4972baa6a1cd822e71ca5de502 is not running
Error response from daemon: Cannot kill container: e4305ffdfe80: Container e4305ffdfe807f5f2c170139244d8899941bfa049fbb1d504ffb2c0f55826c18 is not running
Error response from daemon: Cannot kill container: 60304b2e6b21: Container 60304b2e6b21a5011ef410a22f7ee74f083844a650796e9f05345af7bf3e7f31 is not running
Error response from daemon: Cannot kill container: 88a8b1af385e: Container 88a8b1af385eb635378cd7bf0fe2ae7c5f6aec29f53cd0c2a9b2763e4a512021 is not running
Error response from daemon: Cannot kill container: c7be48ff1e8f: Container c7be48ff1e8f536162c672accd6aeb5a926ddb5a652f4e501424c4a199f05c55 is not running
Error response from daemon: Cannot kill container: 1d4b2d7cd002: Container 1d4b2d7cd00293b3b42a9b302ad1a5858ae9a2fbf18628f36ed0ab6e074781f7 is not running
Error response from daemon: Cannot kill container: 32ba96c808dd: Container 32ba96c808dddaf047f3a8b964c09d48df7e4224df588381b6105be7b6f59642 is not running
Error response from daemon: Cannot kill container: 01d69029a52e: Container 01d69029a52e88588b63453a63e8560540831d4c8b9473a9971f08e887681a3c is not running
Error response from daemon: Cannot kill container: 4e0c07009d14: Container 4e0c07009d14f245753e9f685275119d29aae06fdb653a2b2e8bc078cc2393b0 is not running
Error response from daemon: Cannot kill container: bf8855ecee1d: Container bf8855ecee1d9cbe403b762370366c248eca2471044c73883ca63d3f6c895b8c is not running
Error response from daemon: Cannot kill container: 78182dcd97b4: Container 78182dcd97b4013e5d140219ad986e7d69c113eb4a504a114594e61bb1b11b5d is not running
Error response from daemon: Cannot kill container: 2760b051a614: Container 2760b051a6146e353968a0958f12acaaed75947a0894751d5c38da96c45e8023 is not running
Error response from daemon: Cannot kill container: 24918db55cdb: Container 24918db55cdbff0c66deff19843a2d51c8f2e50ab9ac5b2241cc0934f150759a is not running
Error response from daemon: Cannot kill container: 7639181f6f06: Container 7639181f6f061fda207f5fd9934da5886c406580fa0458900fa070c461cc36d8 is not running
Error response from daemon: Cannot kill container: 3deaaceade5c: Container 3deaaceade5c7292adf3cb768e4c234726ad09dd4198cd00c9b5899fe35be34f is not running