GUI acceptance tests using environment deployed from packages.

Build: #2280 was successful

Job: Onezone basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
21 minutes
Revision
c1f32fd27d328461e823cba8ffae3880e30ca404
Total tests
21
Successful since
#2201 ()

Tests

  • 21 tests in total
  • 20 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  48978      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: 50c192f24d48: Container 50c192f24d4883fb480c56c614d96376bd52ae99a0267b2962ea002efdf93bb0 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-COBTT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/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-COBTT/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-COBTT/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-COBTT/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error: could not find tiller
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
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
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
W0825 23:40:22.662062     442 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  48468      0 --:--:-- --:--:-- --:--:-- 48978
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 06aa894bf3f8: Container 06aa894bf3f8664b1c5017f8f0632d8719a33f09dde994a33c148470c9a5154a is not running
Error response from daemon: Cannot kill container: 46c7f110e7f6: Container 46c7f110e7f6b21a119d77ac4fa1ce927e90d826e4c6affe59717b5ab91d7861 is not running
Error response from daemon: Cannot kill container: f0dcf9dbf6e1: Container f0dcf9dbf6e139fc827edf7d58b88ab81a3982ae1a9bcebae7531272aaf5dc9b is not running
Error response from daemon: Cannot kill container: 3a0c41a17b3a: Container 3a0c41a17b3af326a7b55788df5b69bf3a7a6dd12696718d7d45e08ce0bfe8c5 is not running
Error response from daemon: Cannot kill container: aff184f3541a: Container aff184f3541a771279b4ec093eb5627c2fd5b03d7908a12da1218964efd494f1 is not running
Error response from daemon: Cannot kill container: 5145b3b2ca10: Container 5145b3b2ca1018b3e86a3a7247a0cc6acaaaba3a257c7c2ff772ead78603584c is not running
Error response from daemon: Cannot kill container: 79d919d165fc: Container 79d919d165fcc80f643a525979343d49d8fad695a4a5f30b2126830f672f2035 is not running
Error response from daemon: Cannot kill container: 6d41f465ec3f: Container 6d41f465ec3ffdb748629e5e7b5ba4130f6ad373266c1413f7bec4dc5d1c44a4 is not running
Error response from daemon: Cannot kill container: 978e910c3dd1: Container 978e910c3dd1b03f23ea32485b4d6df146fef3fccf1c85ff04a300092e1843ab is not running
Error response from daemon: Cannot kill container: dc430d2be69f: Container dc430d2be69fd1bd985b1577a29d83859f7af2a5bb4fd8e4fb94c416a5aec8e1 is not running
Error response from daemon: Cannot kill container: 2f8735bdb54c: Container 2f8735bdb54caeaf5bffd40a0af09fc3b1a59502ad61be90d970ef1919b9422d is not running
Error response from daemon: Cannot kill container: 8b38a36a56e2: Container 8b38a36a56e27a2a1fb9bc2af6665ca79db061cf3c7f033a42ac3ad75facfb72 is not running
Error response from daemon: Cannot kill container: 1dcccbb45f59: Container 1dcccbb45f590b565ccf1450417ce172ce9090ff9a6f44bbe90e554d4daca65b is not running
Error response from daemon: Cannot kill container: a34b9c0c3b0d: Container a34b9c0c3b0d030f2f366fa16ea7e587da0efa3a507661d6e2fb0ed4ad84e9eb is not running
Error response from daemon: Cannot kill container: e3e35c693a1c: Container e3e35c693a1c36c965cbaf37ec470400ed8648822703c7c669ed336dd3fb0e3f is not running
Error response from daemon: Cannot kill container: 02a9b8ff0253: Container 02a9b8ff025324107b55605f5a2ad01e4b7ab33db3e216ab6ba863cd9fdebe02 is not running