GUI acceptance tests using environment deployed from packages.

Build: #2149 failed

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

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

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
100  4653  100  4653    0     0  41544      0 --:--:-- --:--:-- --:--:-- 41544
Error response from daemon: Cannot kill container: b68603dd7889: Container b68603dd7889af64fa1953c098b0f3c896dab86859b82d4a91d57cf99a8ea096 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-25 20:51:32,140 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-25 20:51:32,140 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-25 20:51:32,140 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-25 20:51:32,140 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-25 20:51:32,140 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-25 20:51:32,140 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-25 20:51:32,140 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-25 20:51:32,140 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-25 20:51:32,140 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-25 20:51:32,140 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
W0525 21:06:42.952871     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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  14316      0 --:--:-- --:--:-- --:--:-- 14273
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 59a8a06f77ac: Container 59a8a06f77acae8eb82d453584d2cdccf81598d481ab3c59e2cf94c0ecf2eb82 is not running
Error response from daemon: Cannot kill container: 1747c2fda373: Container 1747c2fda373e4554abf43faf5070dbf189366e31689db130f2e045e86a49441 is not running
Error response from daemon: Cannot kill container: 6b0ba68bc108: Container 6b0ba68bc108b915f81b1ae0d4c24601ea5027965a740ca2ff248c7091288d08 is not running
Error response from daemon: Cannot kill container: bbdd7ebab282: Container bbdd7ebab282db3e3fc330aabdc34f316c9bf43039624402ac7a6d47896a3f1a is not running
Error response from daemon: Cannot kill container: 56a03a86a5e9: Container 56a03a86a5e9efffd03a324735d122ab733a6d884493df3a1a612b801686faeb is not running
Error response from daemon: Cannot kill container: 7519b59eefd1: Container 7519b59eefd1499391eab6202337e03fb12bc8bd019be2f640e1ab6f19daf2ff is not running
Error response from daemon: Cannot kill container: e80bba2bbed1: Container e80bba2bbed1ae954b3345af2049253dd2ce33dd1958a66af2e5622008018d45 is not running
Error response from daemon: Cannot kill container: 225276bca213: Container 225276bca2136ddd5dd80bf8c93f192e0dfe1deabf5424d304de524a88ae6328 is not running
Error response from daemon: Cannot kill container: 491f2e38d324: Container 491f2e38d324d537941b241553ad0a6866c520523ec4284b97b2f8311d51e65d is not running
Error response from daemon: Cannot kill container: b74f16dec294: Container b74f16dec294eddde63f1ad5479fb1577ed7fd4e6feaddf3a0d9d4a100ac2e35 is not running
Error response from daemon: Cannot kill container: 67d17bf56841: Container 67d17bf56841ca231373eb905bc8b2c83b42298efabb43befd2c8729fed27da4 is not running
Error response from daemon: Cannot kill container: 1ff88e60e7d3: Container 1ff88e60e7d30df383a8321833be7c969fdf3117f97fb326d4fdac360aa4e18e is not running
Error response from daemon: Cannot kill container: 7c58c42bc50b: Container 7c58c42bc50b25031f1ba5ff458691926149b1d2bae428e12db1594994c79ae8 is not running
Error response from daemon: Cannot kill container: 24b40e78e273: Container 24b40e78e273d9882a5626e0eb35637b479c4952454a333277037ebaa8ab9017 is not running
Error response from daemon: Cannot kill container: f66c9bf079b5: Container f66c9bf079b5d14804ff53a3f16dbeae626bb2eb212f6f7dde7e7f304eef9fe1 is not running
Error response from daemon: Cannot kill container: fb06b731c86b: Container fb06b731c86b8f4193f85486b410760031e6fdbe39785bcff3cf04c9bafededc is not running