GUI acceptance tests using environment deployed from packages.

Build: #2075 was successful

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
28 minutes
Revision
d5330e48531ab5bfbefefb1e446da4fe7cede649
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
100  4653  100  4653    0     0  46530      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: 0967b56bb01a: Container 0967b56bb01a9699113b98af6cf20f4c2040b45795efed2b0b98516ae1d7aee4 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-04 20:44:07,456 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-04 20:44:07,456 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-04 20:44:07,456 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-04 20:44:07,456 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-04 20:44:07,456 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-04 20:44:07,456 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-04 20:44:07,456 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-04 20:44:07,456 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-04 20:44:07,456 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-04 20:44:07,456 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
W0404 20:54:57.553740     441 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  44740      0 --:--:-- --:--:-- --:--:-- 44740
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 96a66fc552ee: Container 96a66fc552eee9e15b64b46417145f642aeb2e9c18fc211d3310317dfc1700c5 is not running
Error response from daemon: Cannot kill container: a68fcc771942: Container a68fcc7719427ba1e29b6da76950e9ebbeed543e2b9787b5efb9b5ad9469e5bd is not running
Error response from daemon: Cannot kill container: 60cdf800a102: Container 60cdf800a10206be2d05af07898cae3c0b70a618c39688706eb2c6c265558f58 is not running
Error response from daemon: Cannot kill container: 26c57b12b838: Container 26c57b12b8381305df00da9934ce24b6ea56a1b47d86d4ea72f21b78e9b5b978 is not running
Error response from daemon: Cannot kill container: cdce1d0697c0: Container cdce1d0697c08aa660d0c2036370f0607f26058b7df82dbd95a6ea2dd98e089d is not running
Error response from daemon: Cannot kill container: 39dc618e56df: Container 39dc618e56dfba609f820dfd93393599f81f917b6fd5ee4ce385e84fb58a54e6 is not running
Error response from daemon: Cannot kill container: df7a5091129a: Container df7a5091129af63fa3597ab0dba5de51663ff5a1f926eef4c3dfc9750e2f4ae7 is not running
Error response from daemon: Cannot kill container: ba48eb419d49: Container ba48eb419d49b7e1eb2de36928989f2815c0ed528f631f28cf29cf6c3e96b2f7 is not running
Error response from daemon: Cannot kill container: 848c1b8270a8: Container 848c1b8270a86712b193366a2a4d3f6f22949ca0dd7c002a680080d48508186f is not running
Error response from daemon: Cannot kill container: fb082daa5e40: Container fb082daa5e408e412ae0aa6d7f382d580255cfe0a6800861667b30af2075c25e is not running
Error response from daemon: Cannot kill container: c3652bdba520: Container c3652bdba5200747766fd71891791f16ee4f10b81402ff8909d532c0a13285d1 is not running
Error response from daemon: Cannot kill container: 71af82a5d834: Container 71af82a5d8349f8f6d22ec73737a144f0a69773e03ec3e2f076003688de8a66d is not running
Error response from daemon: Cannot kill container: 2ecd4ce5515d: Container 2ecd4ce5515d6785562f5f83ba038ca2a89cde7683b05e7858710458f1d0bacb is not running
Error response from daemon: Cannot kill container: 07ab39d84042: Container 07ab39d840420a60d740b608fe1d39436048f7a98d20603877a267cc227035ee is not running
Error response from daemon: Cannot kill container: 7da0496cd4b1: Container 7da0496cd4b1ba1a8e7791ea4e3f65fef4b06378cc71c1bdff05809a66d69072 is not running
Error response from daemon: Cannot kill container: d58002b5d48f: Container d58002b5d48f4a9e00ce7beea7d3146a3550abdefd3a1ca4d8d0455b593deed6 is not running