GUI acceptance tests using environment deployed from packages.

Build: #2023 was successful

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
27 minutes
Revision
2aaf1b1b8b640c119bda95071943fb0ca614c33a
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: ab36a8b5a27a: Container ab36a8b5a27a6a9fe007807670623859a62decaa34256dbdb8c8085a07aa15f5 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-15 09:15:16,323 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-15 09:15:16,323 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-15 09:15:16,323 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-15 09:15:16,323 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-15 09:15:16,323 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-15 09:15:16,323 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-15 09:15:16,323 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-15 09:15:16,323 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-15 09:15:16,323 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-15 09:15:16,323 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
W0315 09:25:37.863933     439 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 --:--:-- --:--:-- --:--:-- 41176
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 7b31f6ef9f1e: Container 7b31f6ef9f1e867398cb1df916d964b1d56164cf7e4ae00702e629dd51489df8 is not running
Error response from daemon: Cannot kill container: da16f290767c: Container da16f290767cd118d109c4009f8d83f7109db609500446ef08c2b01cfdc23c59 is not running
Error response from daemon: Cannot kill container: 3107c0be2833: Container 3107c0be2833f67b59c850763707b3ab2600ce7820f7444c1ca34808bfcdbb66 is not running
Error response from daemon: Cannot kill container: 720ee55a4f08: Container 720ee55a4f089c92a890416e00d01b81219b95e4dbdccbbc9fb5e4ab401f15c3 is not running
Error response from daemon: Cannot kill container: 08c86bb33ac7: Container 08c86bb33ac7fe6dcd7b830e0ef7e20ce681fd0ed9d3d7c60c2f11499629b7d2 is not running
Error response from daemon: Cannot kill container: 97c6b6fb52fc: Container 97c6b6fb52fc40ccd93b28c949f2160e9528bc05e36629d5b381fa011a2cad51 is not running
Error response from daemon: Cannot kill container: 50671901d78f: Container 50671901d78f940c68627d338e3f1c75fcef6177a77845f9b555f678837043ab is not running
Error response from daemon: Cannot kill container: a9f59af7f41e: Container a9f59af7f41e989c52330da5df3ca76baec84e7d544b486487c0c5da3a2c8c78 is not running
Error response from daemon: Cannot kill container: 741a29a350aa: Container 741a29a350aa3511d1891186f384b026f8a5019e100b2b67a9bfc16c6b499bb3 is not running
Error response from daemon: Cannot kill container: 1de85ebf91cd: Container 1de85ebf91cd730800bb348e50af784c17dff1a204af9e398095449a8442a4e3 is not running
Error response from daemon: Cannot kill container: c6fea8e8c98e: Container c6fea8e8c98eee31af7458b11d310c821b3a1bc7701dc80c2863d77f84d39456 is not running
Error response from daemon: Cannot kill container: cffdf7d5baf6: Container cffdf7d5baf623369700080dba6f7bb73adb99351bb9da57c5c440e6763cf051 is not running
Error response from daemon: Cannot kill container: d670efc255d0: Container d670efc255d0f4081d4ab2ad221686c97550c009b12d706528854e02c75a8fd1 is not running
Error response from daemon: Cannot kill container: 8f40cacba2ef: Container 8f40cacba2ef2587a9f90fb17d1d16a52582be1335b83c5065fdb885970ebc43 is not running
Error response from daemon: Cannot kill container: 2e86cbf206ce: Container 2e86cbf206ce1209ff11a94a7f050a38ed883e6887644c0a5a9dc685c5325017 is not running
Error response from daemon: Cannot kill container: 42b5ad03d52c: Container 42b5ad03d52c596b6437863bdb787465d3728aff5c449854ae74dce1caa86fa4 is not running