GUI acceptance tests using environment deployed from packages.

Build: #2030 was successful

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
28 minutes
Revision
c61cc6810335b546aebef8ab3245579ff3653fa3
Total tests
17
Successful since
#1943 ()

Tests

  • 17 tests in total
  • 27 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  48978      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: 6292a7e240a0: Container 6292a7e240a0f7f232f0602ff73125ba0cca27ff8caf7f45f1aace20958cb397 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 23:34:23,621 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 23:34:23,621 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 23:34:23,621 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 23:34:23,621 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 23:34:23,621 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 23:34:23,621 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 23:34:23,621 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 23:34:23,621 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 23:34:23,621 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-17 23:34:23,621 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
W0317 23:45:08.574577     436 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  47000      0 --:--:-- --:--:-- --:--:-- 47000
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: e0278440c129: Container e0278440c129d6bb0aa56dea8a589a4c440c9d28eb66ba5dbd1c9cc8990a9104 is not running
Error response from daemon: Cannot kill container: e023665c60c9: Container e023665c60c9044bcf4930dcd72a9f7210dadaf206f9d14b37dc8f7dc620082d is not running
Error response from daemon: Cannot kill container: 2350a3292dbb: Container 2350a3292dbbe72e48db3208b4f8d048fa0743e90c065efb9ca591addaf784b5 is not running
Error response from daemon: Cannot kill container: 4e82da938062: Container 4e82da9380627bcc11a171c2587ce3ed7c1103a9517809c7ed598652681e5034 is not running
Error response from daemon: Cannot kill container: 4ca7d3405760: Container 4ca7d34057608a79bcc120278345d1840ce03362945449481ea97d001463e97d is not running
Error response from daemon: Cannot kill container: 6cd396ead36c: Container 6cd396ead36c37e76cc5981fcd59e9c61429d4b9ac8508d9829493788dd8acd7 is not running
Error response from daemon: Cannot kill container: f1af8be551db: Container f1af8be551dbe52aa5fecafe49a983900da05d14933a23ff41c755b176e47dc3 is not running
Error response from daemon: Cannot kill container: ed140b966c7e: Container ed140b966c7e96bcfa333373a9f87ff0f3ae11192d42f4e5f456e2cbb0b43172 is not running
Error response from daemon: Cannot kill container: 17e2a7ae01a2: Container 17e2a7ae01a27ee9f5a23afaaad83b6b0485ef214f8fef436f9fdf19b33b3564 is not running
Error response from daemon: Cannot kill container: eb114079f8aa: Container eb114079f8aae4e95153d333002b86ec610db069dbbeb8f0c7bbf87505f54f4c is not running
Error response from daemon: Cannot kill container: 140ab63b7d6f: Container 140ab63b7d6f2701d0796d450734b48be1cf465ab9065ce0a85aaea39d5e3784 is not running
Error response from daemon: Cannot kill container: 2148beea04cb: Container 2148beea04cbb446591fe39cf21f40a592fdb6b67d06378e23d062ef0c36b1f6 is not running
Error response from daemon: Cannot kill container: 71b60604427b: Container 71b60604427b96fbec60601b9644128ce9633dbd413e6cd9fa0b673731f617ce is not running
Error response from daemon: Cannot kill container: 536b0f53ccbb: Container 536b0f53ccbb63bf72d36a8181ffe8fe9c90b9388edd8c003079bb9fdd6f2ea1 is not running
Error response from daemon: Cannot kill container: 52097b5c229e: Container 52097b5c229e740730e5e1b51e24d9f4f4bc6b50ba8fa36d1627059ee2f6385d is not running
Error response from daemon: Cannot kill container: 1f33afe7fff4: Container 1f33afe7fff41185fe069cb975288ec0274652d201c094e02302bd6fec67a3a1 is not running