GUI acceptance tests using environment deployed from packages.

Build: #2280 was successful

Job: Storage sync charts was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
6 minutes
Revision
c1f32fd27d328461e823cba8ffae3880e30ca404
Total tests
1
Successful since
#2269 ()

Tests

  • 1 test in total
  • 5 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  47000      0 --:--:-- --:--:-- --:--:-- 47000
Error response from daemon: Cannot kill container: 863d1cb6f6b3: Container 863d1cb6f6b35c4e436faf26032b1280d22dff77119391d0794ac593d455b62e 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-CSSC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/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-CSSC/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-CSSC/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-CSSC/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 22:57:57.187877     460 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 response from daemon: Cannot kill container: 671987bf6624: Container 671987bf662404b91c55171db02955934f15eae8f55c012f0dcd9585c9a134b3 is not running
Error response from daemon: Cannot kill container: eec7f8f5a2ef: Container eec7f8f5a2eff46a10d45d87216874a9807b5434bc33f476e1403d3fc76f18c5 is not running
Error response from daemon: Cannot kill container: ae6895440878: Container ae6895440878a5e70602099f643d91a307400d156184a495b4b8f377793ad0ba is not running
Error response from daemon: Cannot kill container: 2ac6f8332a8a: Container 2ac6f8332a8a105260dfe445786139a99a1cae37a8dd086c23d4b8de890583fc is not running
Error response from daemon: Cannot kill container: b986ec058435: Container b986ec058435b0e3687407414103a8184e92134d0f22bb75fb8c7da9a159a07b is not running
Error response from daemon: Cannot kill container: 794d94d470f5: Container 794d94d470f5b0f06da43217914b2cc65dec981752fcca7ab90eaa6d7616c693 is not running
Error response from daemon: Cannot kill container: 6cf91ee82c67: Container 6cf91ee82c67acf25041b897791d472021cd5620ac9423b565524e6749dea5d3 is not running
Error response from daemon: Cannot kill container: ce890b085df6: Container ce890b085df6193fb0473c1c706cf3669a71c0c979517c78e0f47e068d3a137e is not running
Error response from daemon: Cannot kill container: 7119f91703a9: Container 7119f91703a92c0459caed6f2227ebdebc2d1fe9ff5745fc15a2fb541e3e04f6 is not running
Error response from daemon: Cannot kill container: 876d15c68c28: Container 876d15c68c28d05e881f3e30dcc805b131c93967f7f10411b5870fb684cd134a is not running
Error response from daemon: Cannot kill container: 1de88c24d8ac: Container 1de88c24d8aceb7de94fd729907e68b9f8f48ccc497b832f678fd4e57a95358c is not running
Error response from daemon: Cannot kill container: ed7164693369: Container ed71646933698668cabd0f1d35d0b25fa170c9f6da89b054e8acb91b90f88a8e is not running
Error response from daemon: Cannot kill container: 9397b5b52041: Container 9397b5b520413a09343dae11aa7509c4188d95cf08833e58d87f50f981663818 is not running
Error response from daemon: Cannot kill container: f5f4f442f0fd: Container f5f4f442f0fd56d110f688b259103a88818b9d0639f55955550ca5025727f0e0 is not running
Error response from daemon: Cannot kill container: 6e544a587a8e: Container 6e544a587a8ec91e3e16d8ba1de3ad25a5d31ad519d30d95f679f3dd85fa4897 is not running
Error response from daemon: Cannot kill container: 62f2e1d013ea: Container 62f2e1d013eab8a38b84c75be69352e660f0b51f8b8a7b3baa1c56f5e3424075 is not running