GUI acceptance tests using environment deployed from packages.

Build: #2009 was successful

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
40 minutes
Revision
003a1be54c506d73a0484428b7f798cfa7e16263
Total tests
17
Successful since
#1943 ()

Tests

  • 17 tests in total
  • 39 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  40460      0 --:--:-- --:--:-- --:--:-- 40460
Error response from daemon: Cannot kill container: 5b24913c5726: Container 5b24913c5726979d321f9126586be3ebcbbab8b7f1fd2ec534e3561b7ce927d5 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-03 16:11:57,308 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-03 16:11:57,308 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-03 16:11:57,308 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-03 16:11:57,308 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-03 16:11:57,308 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-03 16:11:57,308 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-03 16:11:57,308 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-03 16:11:57,308 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-03 16:11:57,308 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-03 16:11:57,308 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
W0303 16:27:55.623059     452 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  38775      0 --:--:-- --:--:-- --:--:-- 39100
Error response from daemon: Cannot kill container: b7d0717124cd: Container b7d0717124cde49e6c70d6d917a1a0cb8aea4ea43412a40e29065099eddc4c2b is not running
Error response from daemon: Cannot kill container: b3a44c42fc05: Container b3a44c42fc05395304c4d630c19fd10ef2f704670e43ad200e249d625ee5c503 is not running
Error response from daemon: Cannot kill container: 529a139e8e5b: Container 529a139e8e5bb450b7ba2779b1ebe8eb654805f8216b16b28daaba7c86789a3b is not running
Error response from daemon: Cannot kill container: 801178abda4b: Container 801178abda4bfc636b7740aa49c064a131432ebb647b96efb2dfcdb17775bf3e is not running
Error response from daemon: Cannot kill container: 7abc5b25ca94: Container 7abc5b25ca94a17ad934dc9181189fb7bbb6d61d6d70d1a7ae2ec1f780fc0a7d is not running
Error response from daemon: Cannot kill container: 94c77afdbc31: Container 94c77afdbc31a4c20270847ca6665f79db1f2457c9b0f0a0620e8fab9bc1c927 is not running
Error response from daemon: Cannot kill container: d879b1b0e18b: Container d879b1b0e18b32b57461e7e6dbb746e3f92e88da1a1ff4c9e012f99ff8be23d9 is not running
Error response from daemon: Cannot kill container: ed9373d635be: Container ed9373d635be76ba5fb78a04f70cdefc6bc461516dbfd05c2b8a3db0d8f99965 is not running
Error response from daemon: Cannot kill container: 198ee414edca: Container 198ee414edca07229d88965390ccd92f3a175d1d633b7ad08ba0b7537ab5fe70 is not running
Error response from daemon: Cannot kill container: 1edbc2a92ae7: Container 1edbc2a92ae72892b35c5e8e9b757209221ad4ced874b7dc5c3ca23366056804 is not running
Error response from daemon: Cannot kill container: cf9582d46954: Container cf9582d46954330e2257471b653e9a5a7010fbdf384e15646aa20a84ba51c9c7 is not running
Error response from daemon: Cannot kill container: 345eb46be7db: Container 345eb46be7db480c7640d3bfcfaa8207b0e983e6ef32f0affe7bfefcc1807b32 is not running
Error response from daemon: Cannot kill container: 71280de56873: Container 71280de56873391a3c180ae46734ecb01a2028d6c92b273b4cb1cb081441ce79 is not running
Error response from daemon: Cannot kill container: e113fe474b93: Container e113fe474b939c3ad59b20f47461417290ee8736ffb9ab332021bcba9eeff372 is not running
Error: No such container: e113fe474b93
Error response from daemon: Cannot kill container: c889ca5f4ff2: No such container: c889ca5f4ff2
Error: No such container: c889ca5f4ff2
Error response from daemon: Cannot kill container: 13383ab9dfe1: No such container: 13383ab9dfe1
Error: No such container: 13383ab9dfe1