GUI acceptance tests using environment deployed from packages.

Build: #2108 failed

Job: Onezone spaces multiuser was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
16 minutes
Revision
616ef003a0a36dc00e59f722ca7550385601e480
Total tests
13
Successful since
#1943 ()

Tests

  • 13 tests in total
  • 15 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  47969      0 --:--:-- --:--:-- --:--:-- 47969
Error response from daemon: Cannot kill container: de503908fee2: Container de503908fee2b2b458dfc10fe2bb092654a7098d77f8048ca46924fa2677b299 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-COSMT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/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-COSMT/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-COSMT/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-COSMT/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
W0420 22:31:46.728131     445 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  34984      0 --:--:-- --:--:-- --:--:-- 34984
Error response from daemon: Cannot kill container: 731f4d478e49: Container 731f4d478e49d1bbddd1d2ec3ea2491ac56788342e7c840b9a0cfb0aece8f42c is not running
Error response from daemon: Cannot kill container: 225c47f15820: Container 225c47f15820e3196bd85f81c8a6855eb69cecf7adaa8a533d234b08aab49abc is not running
Error response from daemon: Cannot kill container: c6ef2d370318: Container c6ef2d370318921a8a06ee75221ccead0ca293cca22df2224557a76a5cb3ae8e is not running
Error response from daemon: Cannot kill container: 91b26c5edbfb: Container 91b26c5edbfb3d80046e60c0165c21d29727bb40c9b93f23d8e6dcccb834a013 is not running
Error response from daemon: Cannot kill container: 8f00013e0a9a: Container 8f00013e0a9a4719fc80ccb98271578c811ad798e6788b1012a51262ed039d76 is not running
Error response from daemon: Cannot kill container: a7a03b7e01d1: Container a7a03b7e01d165392625e9ca23bdc46fce5bdf296be18766f6e369de6342bdcc is not running
Error response from daemon: Cannot kill container: 191f867a3fe2: Container 191f867a3fe247eeae1daceddea01aefd04d9f79549fa920bd33dfa15314dea8 is not running
Error response from daemon: Cannot kill container: ff67bcf71662: Container ff67bcf71662edc5533922bb3f8e6e30bfe11de0398eb82cb0789beb8d746792 is not running
Error response from daemon: Cannot kill container: 6d425f2a80b0: Container 6d425f2a80b0e4dc45a6abf674620b687f587cf64b8be2e92fe7471abf1a1d1a is not running
Error response from daemon: Cannot kill container: 902e4cd8c6cf: Container 902e4cd8c6cfc5ef47cda33b55cdd4e0c137aae3d4e4aab2b0894b13696c5f7d is not running
Error response from daemon: Cannot kill container: ee7071a172e0: Container ee7071a172e0ea75c242a4494a21ee6eeabac186477679e6fff33e786f26d234 is not running
Error response from daemon: Cannot kill container: 16fa08c3cc6c: Container 16fa08c3cc6c96decfd673bbcd3de04931f91dff871ac15b4edd0b994a0dfa09 is not running
Error response from daemon: Cannot kill container: f08c1440bdd7: Container f08c1440bdd72eb1f64d5c3eb362bfb6b6a29dbc87f4886e8a5553a4a376647a is not running
Error response from daemon: Cannot kill container: f18080f21206: Container f18080f21206cb89c38dc5207cc34110134241ba386f247d1e0b595de14f5133 is not running
Error response from daemon: Cannot kill container: f6e3fee87b6f: Container f6e3fee87b6fd883a90192bab8402dab8c92295317d6ecaf31d3880e4b81a63b is not running
Error response from daemon: Cannot kill container: 93e479eeef8f: Container 93e479eeef8fab496afb9a36d9b1476d7db28ecc76df7bdaf538998e622b64ca is not running