GUI acceptance tests using environment deployed from packages.

Build: #2127 failed

Job: Onezone automations was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
19 minutes
Revision
531283e2b89b3833269b775ff1b3609165404e1a
Total tests
7
Successful since
#2098 ()

Tests

  • 7 tests in total
  • 18 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  34984      0 --:--:-- --:--:-- --:--:-- 34723
Error response from daemon: Cannot kill container: 5af8f894f1e2: Container 5af8f894f1e2adf0353f6874defa7941d7eed21bd76e991ea1b6961a2e78df58 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-COAT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/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-COAT/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-COAT/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-COAT/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]
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
W0429 21:55:12.522750     439 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
  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: 46672632d222: Container 46672632d22227938cbc048f449a0dd9a840cd509a2d3fabf03696bdae68b402 is not running
Error response from daemon: Cannot kill container: 47818b3198cf: Container 47818b3198cf21c9776ea9b0ee154bb5269ec6684e23d479389dd4a9571e7222 is not running
Error response from daemon: Cannot kill container: 9f98e8e91414: Container 9f98e8e9141466c4502d26f996b0735e9fe72351c8b2f44a69c2d3c1402ef302 is not running
Error response from daemon: Cannot kill container: b157510040e3: Container b157510040e3715558301fa9a2f954a43333f801426fc30dc4ecf998b77dac25 is not running
Error response from daemon: Cannot kill container: e2f6a2d72b3f: Container e2f6a2d72b3f16e19388baad4abebcacb8044bc815b7ef287d54a1bf41eb07ef is not running
Error response from daemon: Cannot kill container: 836d48f995e6: Container 836d48f995e62c12f28db67b22b214ecc014e1729c697ac7abe1643c04cce5c1 is not running
Error response from daemon: Cannot kill container: b95ab5ab8654: Container b95ab5ab8654af922b5f762df099a79a3d7343ce616ce90e83fe743e99a8ca33 is not running
Error response from daemon: Cannot kill container: d41f03b9c9f7: Container d41f03b9c9f75990a40444a1e22d13b7584f958655058b6f9a7669a128094968 is not running
Error response from daemon: Cannot kill container: 789d2fa9b89b: Container 789d2fa9b89b41978ed9dc8fab0a924cb4da39ffc6e807ea2ebcd578a7f47fc8 is not running
Error response from daemon: Cannot kill container: 2c7ad969d1b6: Container 2c7ad969d1b6c17c6dce9087af57ffc4f3deec5e6ac70564177b955f05e077e9 is not running
Error response from daemon: Cannot kill container: 3eab32b864b5: Container 3eab32b864b596327a42ba4f1f1bf9d6c54a2b61532be7f4b06e6eeba90e73b6 is not running
Error response from daemon: Cannot kill container: 0c8e42e6a8c6: Container 0c8e42e6a8c6bc8985350f22a4d9a3ccccb07153e224b385b214809c59cdbe68 is not running
Error response from daemon: Cannot kill container: e40c69daca82: Container e40c69daca82eff219b0a7b7aaa6848ca0b52eb2c84038e6dd2382909c16d58a is not running
Error response from daemon: Cannot kill container: 315ca37d31a9: Container 315ca37d31a94da464f5894262ff0b08aaee2b175c47db9935ea7e389f7f565c is not running
Error response from daemon: Cannot kill container: cbbd06b7b500: Container cbbd06b7b5000b283d32a2eb086bf5b38a19e9844eee842240dc9082a5bce9a8 is not running
Error response from daemon: Cannot kill container: 739e8b39b1dc: Container 739e8b39b1dc2ff0d8613712a7c0a5f06e5027f4e6f1f76b24bbf03b9715f593 is not running