GUI acceptance tests using environment deployed from packages.

Build: #2143 was successful

Job: Onezone data discovery helpers was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
9 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
Total tests
4
Successful since
#1958 ()

Tests

  • 4 tests in total
  • 8 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  40815      0 --:--:-- --:--:-- --:--:-- 40460
Error response from daemon: Cannot kill container: bebe5388f228: Container bebe5388f22846a54914c28a824526f02f4144a0c1ffe3da6bf7999ad04a73af 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-CODDH/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDH/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDH/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDH/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDH/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDH/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-CODDH/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-CODDH/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-CODDH/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
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]
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
W0518 20:46:34.089331     435 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  29826      0 --:--:-- --:--:-- --:--:-- 29826
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: dddb5f016be3: Container dddb5f016be3de28cbdd08cde2f82d9fd6f17ccbebe909375ae4dc29636464ab is not running
Error response from daemon: Cannot kill container: d4a714aabfe0: Container d4a714aabfe0a187c76d5e035328b33d7f848155e8b366841837c941078de9f5 is not running
Error response from daemon: Cannot kill container: bb2acc0d4d89: Container bb2acc0d4d896a67b5545d3af59e4e68c2bba1762339df97fa7e39b780204849 is not running
Error response from daemon: Cannot kill container: 27af40420626: Container 27af40420626ac9f3982af3bf8fe8d20442dfbd5aa0a649861367cf95f4ddaf5 is not running
Error response from daemon: Cannot kill container: de6c17d54807: Container de6c17d5480793332a612b31aecc5ff8e045ff19531cbdb45a9500b85af83af1 is not running
Error response from daemon: Cannot kill container: 6a96f09e0b90: Container 6a96f09e0b90d5fe03f3fa7c7f9aa7b3cdbc6c1ee14ffb4563387c67abbe6e46 is not running
Error response from daemon: Cannot kill container: 22e2706c06ee: Container 22e2706c06eebc19e5791d4c3ba43d213152043d7e33e8b9c1c329bddacfee9e is not running
Error response from daemon: Cannot kill container: 6b60097d4982: Container 6b60097d49826ea471c542d1de24b5dde4e480734ba69fab912a6649479616b5 is not running
Error response from daemon: Cannot kill container: 714e825c1110: Container 714e825c1110ae4e4d59b307179208ff8e7fb916b3aec336266b2387b30ab467 is not running
Error response from daemon: Cannot kill container: d4525cb61c88: Container d4525cb61c882730069c6bfa005f390a3beaf1a1ce4fdf438159086a30cb33d9 is not running
Error response from daemon: Cannot kill container: 753e016c01e5: Container 753e016c01e5c252abe73cf24b8d3813434d8531e3a369968182fd8257ae7e4c is not running
Error response from daemon: Cannot kill container: 00539f04b5f2: Container 00539f04b5f2ddd666b7e31481e2b0d26415cfccd3e3fd2d6505f72cf16198cf is not running
Error response from daemon: Cannot kill container: a54d85a38c7a: Container a54d85a38c7accdb2c75c4f13167a1161af24a30a4e57442e79555a4056f9605 is not running
Error response from daemon: Cannot kill container: 9a9112f834f0: Container 9a9112f834f079731854f27df67f58a218d21a9961cd52ec809ba68d7c7ba4ce is not running
Error response from daemon: Cannot kill container: 0cb99e3e7f81: Container 0cb99e3e7f81c5d14f7018b9297fa306b76999a18d5e4e76997cb66a71c54df8 is not running
Error response from daemon: Cannot kill container: 6f7c858ff8f7: Container 6f7c858ff8f79bbff51d0e839d2a22162c6eb77e1794486e5c6027709b20b0b7 is not running