GUI acceptance tests using environment deployed from packages.

Build: #2043 failed

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
37 minutes
Revision
d4a37ebda8d9cad234b655aae75d29294552ebb5
Total tests
17
Successful since
#1943 ()

Tests

  • 17 tests in total
  • 35 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  35250      0 --:--:-- --:--:-- --:--:-- 35250
Error response from daemon: Cannot kill container: b90c293ef400: Container b90c293ef400e4f07a0cb2de8853b1c6776aef9f9d5c408b9ae963825c18be35 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-22 19:52:21,922 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-22 19:52:21,922 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-22 19:52:21,922 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-22 19:52:21,922 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-22 19:52:21,922 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-22 19:52:21,922 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-22 19:52:21,922 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-22 19:52:21,922 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-22 19:52:21,922 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-22 19:52:21,922 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]
W0322 20:06:49.523073     444 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  27696      0 --:--:-- --:--:-- --:--:-- 27696
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 92efd4f8b267: Container 92efd4f8b267444ec830900f5c3330b3cbac7ecf686479b072f7c30515c7f7b2 is not running
Error response from daemon: Cannot kill container: db0d3e32979a: Container db0d3e32979af36f0f6f6fd1b2bbe59fe0d776ab39915841f152eb97bfacb5cf is not running
Error response from daemon: Cannot kill container: f473c6d49967: Container f473c6d49967238c601d7472b110efc8a7eb5a5ffb84c7e8f9adcbbb386759fa is not running
Error response from daemon: Cannot kill container: 45b92a4c57cf: Container 45b92a4c57cf48aecf14aa2b6b020a6cf4ca8fc6ad8a1798510c5633bfb3c690 is not running
Error response from daemon: Cannot kill container: 51e34759c710: Container 51e34759c71002eaea684d6d877e80640a00a97842d28f9184ce3e0153d4ce6c is not running
Error response from daemon: Cannot kill container: 299da2166e37: Container 299da2166e379850138b70c9638f1a4c48a9ca2955b494677f903e8d771e405e is not running
Error response from daemon: Cannot kill container: 0225c8993d17: Container 0225c8993d170e0691090af512345c731c8d79feec2086c9fb53a30bafdc7c49 is not running
Error response from daemon: Cannot kill container: 4689a916649f: Container 4689a916649f899d0cc4ad80b502ede0fe6cab94e929ce8146019671c62e5371 is not running
Error response from daemon: Cannot kill container: f92d5cf5a925: Container f92d5cf5a925fd4e57c551ec2e0cd3af14a5836d135ea87fbe70b297ec5d0a2d is not running
Error response from daemon: Cannot kill container: 4f67fb539b2f: Container 4f67fb539b2f2b1a9c5c33b9f172ad44c4ba018b466869c2dbcda5d2f76aeca9 is not running
Error response from daemon: Cannot kill container: 67654cad9bc3: Container 67654cad9bc3d5135d3d0408a7328e29e2b36fdac1e656069448d3bd9e80694d is not running
Error response from daemon: Cannot kill container: 2dc2f32d8808: Container 2dc2f32d8808e2995bdd776dc9eb13e384280e8e1a7244dacda65fcb529148de is not running
Error response from daemon: Cannot kill container: 56a1e761fd66: Container 56a1e761fd66a42663b915f287584d1a52fd427d7d64cbe796d4026013085f8d is not running
Error response from daemon: Cannot kill container: 14560f516311: Container 14560f5163115358ca1485707c1ca9ef9178a9927c0566968c993d663e0fdf4a is not running
Error response from daemon: Cannot kill container: af017152ebd6: Container af017152ebd690aa03b2ce0bcaab5c1b6945ba6ccfb2995ddd50c4ca588a4c47 is not running
Error response from daemon: Cannot kill container: 9417696bd614: Container 9417696bd6147858d42d18d0554c0a18bcfaeba27a4a68e5278031b36630c94b is not running