GUI acceptance tests using environment deployed from packages.

Build: #2080 failed

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
39 minutes
Revision
207c1bbc34a1557072ac46d0e532f97497c6e829
Total tests
17
Successful since
#1943 ()

Tests

  • 17 tests in total
  • 38 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  42300      0 --:--:-- --:--:-- --:--:-- 42300
Error response from daemon: Cannot kill container: 748207e59f01: Container 748207e59f01447286bcf338434a2b0aff92d1ec81dd14bc0268fc8f22dbdc40 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-04-05 17:55:32,723 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-05 17:55:32,723 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-05 17:55:32,723 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-05 17:55:32,723 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-05 17:55:32,723 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-05 17:55:32,723 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-05 17:55:32,723 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-05 17:55:32,723 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-05 17:55:32,723 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-05 17:55:32,723 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
W0405 18:11:01.726895     457 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  32089      0 --:--:-- --:--:-- --:--:-- 32089
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 7b0f21552ae5: Container 7b0f21552ae5cc6321996fc21f2086e52739a9dd5070e6245bd8c0efe8742c40 is not running
Error response from daemon: Cannot kill container: 115d661e546b: Container 115d661e546bdd5e79f484fda7d0a5edda04c1563d863a966e65a00c4e2cf0d0 is not running
Error response from daemon: Cannot kill container: bcb598ea6a3b: Container bcb598ea6a3b4f910c065bebb051b6b22b1e9a05569d07b2332cd2dccda7de5f is not running
Error response from daemon: Cannot kill container: 3462b169843f: Container 3462b169843f5eb1530c2860843737822afbbc5f970fbc55b5714da9c138034c is not running
Error response from daemon: Cannot kill container: 58e893b6331b: Container 58e893b6331bcd6f76b5b676dfffe557c4cff46ff4d582604af1a610a389733c is not running
Error response from daemon: Cannot kill container: 3ed9925a471d: Container 3ed9925a471d6627f6119737a2f02211c77e666fa6d850258669b609769f1122 is not running
Error response from daemon: Cannot kill container: 25d25700930a: Container 25d25700930afee6f72c0c0b69d6f59a7c86b811ca3c41d26975c43dfcdc6c37 is not running
Error response from daemon: Cannot kill container: 47320c91842b: No such container: 47320c91842b
Error: No such container: 47320c91842b
Error response from daemon: Cannot kill container: 3784d3b6e0b7: No such container: 3784d3b6e0b7
Error: No such container: 3784d3b6e0b7
Error response from daemon: Cannot kill container: 13ea70108118: Container 13ea70108118c98cf2d5c19e6e879275c7effcbc111c8dbdad3255bcca594dc5 is not running
Error: No such container: 13ea70108118
Error response from daemon: Cannot kill container: 198f9e2c1e17: No such container: 198f9e2c1e17
Error: No such container: 198f9e2c1e17
Error response from daemon: Cannot kill container: 5ac7854a3d11: No such container: 5ac7854a3d11
Error: No such container: 5ac7854a3d11
Error response from daemon: Cannot kill container: d9ba4157f64e: No such container: d9ba4157f64e
Error: No such container: d9ba4157f64e
Error response from daemon: Cannot kill container: 15dd9985d7b2: No such container: 15dd9985d7b2
Error: No such container: 15dd9985d7b2
Error response from daemon: Cannot kill container: c6b9999dae04: No such container: c6b9999dae04
Error: No such container: c6b9999dae04
Error response from daemon: Cannot kill container: 1cd9cb673f3b: No such container: 1cd9cb673f3b
Error: No such container: 1cd9cb673f3b