GUI acceptance tests using environment deployed from packages.

Build: #2029 failed

Job: Onezone invite tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
25 minutes
Revision
c61cc6810335b546aebef8ab3245579ff3653fa3
Total tests
9
Successful since
#1969 ()

Tests

  • 9 tests in total
  • 24 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 --:--:-- --:--:-- --:--:-- 47479
Error response from daemon: Cannot kill container: 2cbf988d2d3a: Container 2cbf988d2d3aa021c2090a3c0a7da4c95e8969bbf32ef42fec9ba9c7af41dbe7 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-COIT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/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-COIT/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-COIT/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-COIT/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Unable to find image 'onedata/acceptance_gui:v8' locally
v8: Pulling from onedata/acceptance_gui
a1298f4ce990: Already exists
04a3282d9c4b: Already exists
9b0d3db6dc03: Already exists
8269c605f3f1: Already exists
c810ae7364ef: Already exists
78d356e6ec21: Already exists
792b20546d07: Already exists
c1d3130a77b3: Already exists
0c7ad6b015da: Already exists
114ec36e4007: Already exists
2bc588dde0c7: Already exists
89641d7ca7e2: Already exists
b6cd4b44aa19: Already exists
e1c77802a505: Already exists
f373aa611054: Already exists
Digest: sha256:97e4de524ef380ad8c07bf6c71280c378a5e0179834942ff0e6c0007d32b148c
Status: Downloaded newer image for onedata/acceptance_gui:v8
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]
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
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
W0317 22:36:32.922936     492 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  47969      0 --:--:-- --:--:-- --:--:-- 47969
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 5fc383f75772: Container 5fc383f7577205e0a2dd144b1a57642370a913dac57d25bd25714297e1d03e57 is not running
Error response from daemon: Cannot kill container: a0079bc499cb: Container a0079bc499cbc4ba1db2b01b892601a58b9ce6821ac4537ee14e98cd34a576fc is not running
Error response from daemon: Cannot kill container: 4ece3ec67231: Container 4ece3ec67231ac80380fbeb0d389593b9cd7ea82f7020d74d562e850b6868462 is not running
Error response from daemon: Cannot kill container: dfd3cee1c19e: Container dfd3cee1c19e550f09db098d1aac734b56a42afd10a8f492b7422be1b3797de9 is not running
Error response from daemon: Cannot kill container: 1d681ee81661: Container 1d681ee816613194713af5d36ec50ac3043a11e39c202b1172aaa0f2467f299c is not running
Error response from daemon: Cannot kill container: 7f01a03dbcfb: Container 7f01a03dbcfb1524fe6c928760be6b4ad6c2b895cb7b45e0d17e94cf596737ce is not running
Error response from daemon: Cannot kill container: da289136f312: Container da289136f312276ea9be124625711b43e6a31b660b3e63d7322eef908f8b299a is not running
Error: No such container: da289136f312
Error response from daemon: Cannot kill container: 4ede4d716e22: Container 4ede4d716e22a96939f53c948371ff02e8b7795d84094137122bd450a19cce15 is not running
Error: No such container: 4ede4d716e22
Error response from daemon: Cannot kill container: 873822f97f9a: Container 873822f97f9a1053f0211b0bf103da073425dde44149222072185e3f1c1459dd is not running
Error: No such container: 873822f97f9a
Error response from daemon: Cannot kill container: 9f3a8715d5bd: Container 9f3a8715d5bdea8d77c793582fb01ebc1c826c35418041ed318ec3f769bba4a6 is not running
Error response from daemon: removal of container 9f3a8715d5bd is already in progress
Error response from daemon: Cannot kill container: 5390afb5f31f: Container 5390afb5f31f6d524908a003e44bb9ceae856ed0a90055bb0af3f74c04319621 is not running
Error response from daemon: Cannot kill container: c6c5e40b2499: Container c6c5e40b24993ef8bdb1fbed63111019c1e61cfe637af10dd2acf963b2d481bb is not running
Error: No such container: c6c5e40b2499
Error response from daemon: Cannot kill container: 6cdbc124847c: Container 6cdbc124847cb5487ab1e91f0ff470886eaf8139042287835ef8f80e7ddcd854 is not running
Error response from daemon: Cannot kill container: 6a9862fad8d1: Container 6a9862fad8d158ad0877d50497381c78ddf03434b79364037303d425a8808e9c is not running
Error response from daemon: Cannot kill container: 26f891bb3742: No such container: 26f891bb3742
Error: No such container: 26f891bb3742
Error response from daemon: Cannot kill container: a3f319d966f9: No such container: a3f319d966f9
Error: No such container: a3f319d966f9
Error response from daemon: Cannot kill container: d71a7669dca7: No such container: d71a7669dca7
Error: No such container: d71a7669dca7
Error response from daemon: Cannot kill container: 59bcc9ad5316: No such container: 59bcc9ad5316
Error: No such container: 59bcc9ad5316
Error response from daemon: Cannot kill container: 819a49f6b7eb: No such container: 819a49f6b7eb
Error: No such container: 819a49f6b7eb
Error response from daemon: Cannot kill container: 7e2c1d939b3a: No such container: 7e2c1d939b3a
Error: No such container: 7e2c1d939b3a