GUI acceptance tests using environment deployed from packages.

Build: #2147 failed

Job: Multiprovider basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
20 minutes
Revision
55cdb7fe92fff892fdb8cf16f00c4ce6627a4c4a
Total tests
8
Successful since
#2082 ()

Tests

  • 8 tests in total
  • 19 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  44740      0 --:--:-- --:--:-- --:--:-- 44740
Error response from daemon: Cannot kill container: 093033ba1477: Container 093033ba14778f38d8a852fda1a32c92a64ef3de1996f1945b13e43a006fd492 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-CMBT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/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-CMBT/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-CMBT/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-CMBT/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]
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
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
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]
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
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  47479      0 --:--:-- --:--:-- --:--:-- 47479
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: fce84ee57c5c: Container fce84ee57c5c9553cdaf94bd1e06c1da06832f44ab2d58e964095759af181586 is not running
Error response from daemon: Cannot kill container: 4af0447d7a98: Container 4af0447d7a987cfb092d9ac6108f3591648d6a260e1971cd84f85cf3bbb3c084 is not running
Error response from daemon: Cannot kill container: 904367a864cf: Container 904367a864cf64eb7615e818a5d9ad0e4b573da1e5ef2439ca561f7ac23d4e2e is not running
Error response from daemon: Cannot kill container: e54bf9bd7834: Container e54bf9bd78344e0c07b2410eba5f7f9b04a190011a755f0afdb9025c968e9a91 is not running
Error response from daemon: Cannot kill container: 8d5610a49dd8: Container 8d5610a49dd83828342238983b7fffeef145e2ff163f09eb64fd8d2cefd577e7 is not running
Error response from daemon: Cannot kill container: 3b11822a2faa: Container 3b11822a2faafebbe93b6d66879f0bc0fdbbd5e3f9d13b441666aa03079c3c96 is not running
Error response from daemon: Cannot kill container: d88de948c7f9: Container d88de948c7f931a6208350f2c68ecb12c471491e1179eea5f87abe92b8561be8 is not running
Error response from daemon: Cannot kill container: a0c07031d373: Container a0c07031d373023aeb2369d78e8c31528d8217e1344b6e27d10a0078a986c884 is not running
Error response from daemon: Cannot kill container: 32ccced98081: Container 32ccced98081592d5104b2441ad19528b282621ec1c24e1584eed64a17c2303e is not running
Error response from daemon: Cannot kill container: 47ec8444c314: Container 47ec8444c314f6c1c904ff529226b7d126914b497e7736983b307b72161adc4d is not running
Error response from daemon: Cannot kill container: 6735c6629653: Container 6735c66296530dcb801af643cd2edbd1b962ee73c7001045fc18b7b8e20f4b70 is not running
Error response from daemon: Cannot kill container: 5c417c85691a: Container 5c417c85691a769dd1dfcb36acc3bb1b9e0a6f78a7d107c8a065552ead0cc54c is not running
Error response from daemon: Cannot kill container: f791d4f33651: Container f791d4f3365168f72a2de767092ca20d8facfa77a3c14bbea564ef7a50b688f6 is not running
Error response from daemon: Cannot kill container: d2f181727e83: Container d2f181727e83af495d603130e542cf2562f1ae8583f3a3f61d98783bd1a31c4c is not running
Error response from daemon: Cannot kill container: 0a15179f4f70: Container 0a15179f4f708f1ef282a0af0b817197d8f331d7503bc99688c350b78ad523e9 is not running
Error response from daemon: Cannot kill container: 0f9963be6a2b: Container 0f9963be6a2b68c6bd6ee11e2035556529c916933fc86ffb0bc7f211179ade75 is not running
Error response from daemon: Cannot kill container: 00c36219c003: Container 00c36219c0037867f4a9265bc6a140bd8066df051c0e8c8989a626e14437c730 is not running
Error response from daemon: Cannot kill container: cbdcde5bbcc3: Container cbdcde5bbcc31bf46a85cb4c2315c2d101196c03f15667ae3af19bfd6c019676 is not running
Error response from daemon: Cannot kill container: 396ceb21f9d3: Container 396ceb21f9d30bca6a0473c3be5109314f4ea5e74e85d6622b0f46ea5d141df7 is not running