GUI acceptance tests using environment deployed from packages.

Build: #2009 was successful

Job: Onezone invite tokens with caveats was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
17 minutes
Revision
003a1be54c506d73a0484428b7f798cfa7e16263
Total tests
4
Successful since
#1958 ()

Tests

  • 4 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  41176      0 --:--:-- --:--:-- --:--:-- 41176
Error response from daemon: Cannot kill container: c94541ccdd39: Container c94541ccdd39124c0bb2f3ad4d4df86a6b0867bc17b58335b17631f29d6f9771 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-COITWC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/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-COITWC/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-COITWC/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-COITWC/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]
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
W0303 16:11:57.455261     487 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  30411      0 --:--:-- --:--:-- --:--:-- 30411
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 9fb3e97a3d18: Container 9fb3e97a3d1857adefb9e338b1af7867471c16e240c919ab35f4fab3e1190fb8 is not running
Error response from daemon: Cannot kill container: 85e49f5887d4: Container 85e49f5887d45ecf01e7baa630bac78ee8dfc11935cf41284a49087d916d9ad6 is not running
Error response from daemon: Cannot kill container: 386c4f717592: Container 386c4f71759209c397f908a2503fa8680d2b90b072a1f16fba486908f5a61d61 is not running
Error response from daemon: Cannot kill container: 63527ee539e4: Container 63527ee539e448e4fec7008cb91e30b06819ec7a9c1804022cf239a573e3ec05 is not running
Error response from daemon: Cannot kill container: ee81238af4d0: Container ee81238af4d0cfffdcce053cdc86c49eb2560da7f1dd5387e26427d506dd5b62 is not running
Error response from daemon: Cannot kill container: 26ff31503508: Container 26ff31503508949a77cbcfea383ccad6db415ac5d6b5480f7f3a797cea96ce46 is not running
Error response from daemon: Cannot kill container: 6b136e7ce960: Container 6b136e7ce96071793ec73875bf468f45704b22f7657b3b6c539b440a4283304e is not running
Error response from daemon: Cannot kill container: 90e96c70783f: Container 90e96c70783f788b536a4691118caad13064321d4ea8f08c6b886c0830f558b4 is not running
Error response from daemon: Cannot kill container: 0ad4dbbd18ce: Container 0ad4dbbd18ce3549d42b6abbe4b8fe0ebeeca7e49d1e60a976394c136590e506 is not running
Error response from daemon: Cannot kill container: facf8701b7ed: Container facf8701b7edf1073c05c195bed666414cff408ceb16d0bc8362072c892a18fd is not running
Error response from daemon: Cannot kill container: 4e14713bd200: Container 4e14713bd2006e327eef755fcf1b8d8d6882949de5a60246c8ab1dc7594818a8 is not running
Error response from daemon: Cannot kill container: 91ca156113d3: Container 91ca156113d3ff7c25f6d81a67e44e34f41882c880f45a53611cf5cca19d09e9 is not running
Error response from daemon: Cannot kill container: b71a5a4f0b3a: Container b71a5a4f0b3a156414b80365ae3cf9974ce5a22bdfd44650741534949a3a1dec is not running
Error response from daemon: Cannot kill container: 58b5d959206f: Container 58b5d959206f2558cb0278d1752628c6e9d6429da92dd2328a1f2bc729f54996 is not running
Error response from daemon: Cannot kill container: ad78097563ad: Container ad78097563adbd83db0e5715f0f2640e4e664caf338d14407b8ccf59ebdd580c is not running
Error response from daemon: Cannot kill container: c1181be1dbd8: Container c1181be1dbd85a7f61a12fd21aaa9cd04e30060fc7f2ab40571cef2a6cbb17d6 is not running
Error response from daemon: Cannot kill container: 6d8ca50bc51a: Container 6d8ca50bc51a2661e9b5b459ce156733dd70f943f45d1ed0ae89c650ab32eaa4 is not running
Error response from daemon: Cannot kill container: eadb91f98cbd: Container eadb91f98cbdf8ab2e4c1227db6afb5e6483879c962ef79a301e828d5eabe768 is not running
Error response from daemon: Cannot kill container: 3aad81ce769c: Container 3aad81ce769ca5a906ace5f0d636e085f108797a99367c7d513b2d953f27eeef is not running
Error response from daemon: Cannot kill container: a9ec3e832ee0: Container a9ec3e832ee00e1f5d3e79997a9bd60619db36e051311456c0970cafa108393a is not running