GUI acceptance tests using environment deployed from packages.

Build: #2028 was successful

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
27 minutes
Revision
06b7ddbe39e2302126bded895dfde2e9f3fa8004
Total tests
17
Successful since
#1943 ()

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  48978      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: 53d6d509e831: Container 53d6d509e831eed15b39f37a578281211b3e90438ac81201d12ddfac29102818 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-17 09:28:45,785 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 09:28:45,785 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 09:28:45,785 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 09:28:45,785 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 09:28:45,785 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 09:28:45,785 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 09:28:45,785 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 09:28:45,785 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 09:28:45,785 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 09:28:45,785 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]
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
W0317 09:39:08.063577     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  45174      0 --:--:-- --:--:-- --:--:-- 45174
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 6166df0f043b: Container 6166df0f043be7f833f2eec3fded1fd147a03fd9c42fc87b0603095c0968dbec is not running
Error response from daemon: Cannot kill container: 565e89c7e5a1: Container 565e89c7e5a193ae1be296532dfb56ccdc91c9c6b6ead206ba3fd9379f7d12fb is not running
Error response from daemon: Cannot kill container: 8a23f770fb69: Container 8a23f770fb693c508bc2d3cb9e25985d9927f3738c34089c86c633d900ad075f is not running
Error response from daemon: Cannot kill container: 34ff62fd5c2d: Container 34ff62fd5c2d176a2b7f6936ac51d537a40d11b39a0b0cdc678744012ef5487f is not running
Error response from daemon: Cannot kill container: e87f0b383435: Container e87f0b3834355977f1d9ddea8c9976128caf9c2698704b305973c177ee34d751 is not running
Error response from daemon: Cannot kill container: 2e3cd50bfa5c: Container 2e3cd50bfa5c1cb1c51da8d7aa4184f2b21069de2867d20f16c01d070523a36a is not running
Error response from daemon: Cannot kill container: 84b0eba2ef36: Container 84b0eba2ef368e4047870d786de7dc2e7ced3be1f26a00e99b7eca4c0f75c31b is not running
Error response from daemon: Cannot kill container: f0e1275316ec: Container f0e1275316ec81d15e6611a2d49be835c5ba15b1dd185605611b4569afb40e60 is not running
Error response from daemon: Cannot kill container: 03243e8bb01e: Container 03243e8bb01ebfc58f7902b60023762fcd2c419b719e6f1053f914cdf85d71b2 is not running
Error response from daemon: Cannot kill container: 9f90ed5a301c: Container 9f90ed5a301c9918b813736240f4511592aca304429921bc028588c56ad93a0f is not running
Error response from daemon: Cannot kill container: 28095c3b7c85: Container 28095c3b7c852dd6e47f5f3422eac05b0701e565ed70b8889721c2099bf3f34a is not running
Error response from daemon: Cannot kill container: 319f63ea7596: Container 319f63ea759685bb6c4a9009ccd1f3393bdfb390fa73b6567f98fd1e6a7885fc is not running
Error response from daemon: Cannot kill container: 3c463ad085cf: Container 3c463ad085cf6f3670e3723e6c33aae50aed58d4deeca9f02751bc85568e15dc is not running
Error response from daemon: Cannot kill container: bd5d3953d164: Container bd5d3953d164632b24f6154527b3aa84ba57de376fcdd8a770378efc2ffe4aba is not running
Error response from daemon: Cannot kill container: 29813652a60b: Container 29813652a60bc57afabc82d434f6ca7dcbb30c5c626a0bacf780124b4a4cc1db is not running
Error response from daemon: Cannot kill container: b98c567f5e41: Container b98c567f5e41d0631a7f8c049405ad7ac8f51532c146774efc7e3a77489b4b21 is not running