GUI acceptance tests using environment deployed from packages.

Build: #2008 failed

Job: Multiprovider basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
29 minutes
Revision
0ab5f662c3ea6d31c3ccedd9a5babeeb1a2cc8bc
Total tests
8
Successful since
#1990 ()

Tests

  • 8 tests in total
  • 28 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  43896      0 --:--:-- --:--:-- --:--:-- 43896
Error response from daemon: Cannot kill container: f11c2bae6c5a: Container f11c2bae6c5a171bbffe50dae341cccd44e04d67ba2cde85b1792a0def60465f 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)
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
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  40815      0 --:--:-- --:--:-- --:--:-- 40815
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 4970761a0348: Container 4970761a0348e848b253d10677fedafc8871d5511fa00d363ef281a81ea4d147 is not running
Error response from daemon: Cannot kill container: 4f8e1dc0545a: Container 4f8e1dc0545accff38937ff6278602d759021b90f55fa32c501678348052f0b1 is not running
Error response from daemon: Cannot kill container: 25bfed7c5380: Container 25bfed7c53809a3940e3a542b6aa3bd65044664ff734bf6d1fa82efe286b6289 is not running
Error response from daemon: Cannot kill container: af8db4e33460: Container af8db4e33460f5bdab15c71242b00b9618e2bc18e61ebaa631cabff7916f8366 is not running
Error response from daemon: Cannot kill container: d1aa7ad562da: Container d1aa7ad562dadfb7dc553212b71472b01de8566343ca2ce0268c5bf1559a2406 is not running
Error response from daemon: Cannot kill container: 308afe20ce59: Container 308afe20ce59eaf1adad1273d558e98b1dbe713a7442be6da30fd6e79cc4c009 is not running
Error response from daemon: Cannot kill container: d0680a57b656: Container d0680a57b6560293ff94d641c7baac749102e467fe01ef501d35847ce07721f3 is not running
Error response from daemon: Cannot kill container: ac744a58f2f3: Container ac744a58f2f319e6cfd05060172128fb95a779ad892fc40bccfcf29aa2e69611 is not running
Error response from daemon: Cannot kill container: 8738514e99e0: Container 8738514e99e0eaab3c7fd5a387a22306b2e814ff947e10a617340e3bd70abe9d is not running
Error response from daemon: Cannot kill container: 0fa8dce8cf80: Container 0fa8dce8cf806bbe0e7e606b52ab680ec80a51476fabbe2219e9b4eac0711b4f is not running
Error response from daemon: Cannot kill container: 8dbde2cf2504: Container 8dbde2cf250415e6c9e264d384117664c15844902489503ac7bd0114bc6c7af6 is not running
Error response from daemon: Cannot kill container: 51bbf7a5cce5: Container 51bbf7a5cce5bae2df757a92243337a4160c844354156fc29cda342d35121652 is not running
Error response from daemon: Cannot kill container: b482b1660510: Container b482b1660510505c37abe16da345276a9cc3480f1b201bf89dd864084f340cac is not running
Error response from daemon: Cannot kill container: 9fdc1f9cbbe2: Container 9fdc1f9cbbe2fe4bbc7668088034c12e0b33fedf636b151d2493c391fb2c7d23 is not running
Error response from daemon: Cannot kill container: a606f50b426c: Container a606f50b426ca5d6a25f13b2aaef8b31e22d791ec41055ed142ef0e8f75d4a4b is not running
Error response from daemon: Cannot kill container: d2ada6ac6336: Container d2ada6ac63367f0f452827917f9921dd98c3a421044f23483858dada4e98814f is not running
Error response from daemon: Cannot kill container: 18f78f6814b0: Container 18f78f6814b0f93d8c6d798c8b0ff9e54f4660f1ed812a0a95fda6068229d022 is not running
Error response from daemon: Cannot kill container: 3e22790a5e99: Container 3e22790a5e9942024a8ae134f6fa52167bcfac3d8aafd0bda0f8672ae5d0a3e1 is not running
Error response from daemon: Cannot kill container: ba563284c9f6: Container ba563284c9f694126509fcf8c31bbb662e14d7adb574fb23e9302708e926f3c7 is not running