GUI acceptance tests using environment deployed from packages.

Build: #2130 was successful

Job: Onezone invite tokens with consumer caveats was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
27 minutes
Revision
39fb434fa4268b56f32dccaa52527f3591cd9ea8
Total tests
9
Successful since
#2082 ()

Tests

  • 9 tests in total
  • 26 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: b92891758b1c: Container b92891758b1c36cd63efbcd69ca36af9a6c61329bd757efa169a982776c1ab0f 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-COITWCC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWCC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWCC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWCC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWCC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWCC/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-COITWCC/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-COITWCC/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-COITWCC/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)
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]
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
W0504 20:28:14.078857     506 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  36069      0 --:--:-- --:--:-- --:--:-- 36069
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 1e8028208eb6: Container 1e8028208eb65eeb77244e8ffcd0c3f606f1f15d3a6ea31132d23dab7b5ea1a1 is not running
Error response from daemon: Cannot kill container: 65489fb9274d: Container 65489fb9274d678da607b50c98fa5a012f79e66ccc129000bb291ba1fdb1a2ae is not running
Error response from daemon: Cannot kill container: 30a10340b857: Container 30a10340b857bdb87a8241d72b6da89a7334a624d0ae266120ce1e54466e4537 is not running
Error response from daemon: Cannot kill container: 1c75e35019ae: Container 1c75e35019aeb9b0b822f76758d0fe5047539031fe2d1ca2f7cc0eb5bfb780bb is not running
Error response from daemon: Cannot kill container: 0cf0908a39d7: Container 0cf0908a39d79793d9f05577a1a5e049790b9e47a584c98cc56b792fa0ecc128 is not running
Error response from daemon: Cannot kill container: 651b5e026f29: Container 651b5e026f29aefe5362e882833a80df461caede3fc6f256d4cd420d4aa7ddac is not running
Error response from daemon: Cannot kill container: a81f64f5b27b: Container a81f64f5b27bffa41764fea3b66b13a2b50da9bd50679124622b0ddaf1dab083 is not running
Error response from daemon: Cannot kill container: c679f22df931: Container c679f22df93158309fe2e1dc1fae2705e09025979f3a252462b8a02f35fef9f8 is not running
Error response from daemon: Cannot kill container: fdc083199824: Container fdc0831998247c903c086308d7c8f3543bc4374d0125d83a1f14b66b1ab09996 is not running
Error response from daemon: Cannot kill container: 5292dd70bb7a: Container 5292dd70bb7ab45a2e7cf37ec998ce770d9bc7b28b49b152ff676811a3700dee is not running
Error response from daemon: Cannot kill container: 9f0a2ee577cd: Container 9f0a2ee577cdb28944a68aa7a9bb2595f4677c5ce96d31759c3b018b71ffd7fd is not running
Error response from daemon: Cannot kill container: 4b2ff1115acd: Container 4b2ff1115acd902e62a7f0a6e14578854afb5a9c38313a1fc6fdcc6c224690e4 is not running
Error response from daemon: Cannot kill container: e55a96827da8: Container e55a96827da8daed8aa6996ae9acd83cf065f8a796de613503cce9f8d67b7274 is not running
Error response from daemon: Cannot kill container: e7e0e6f3ad4b: Container e7e0e6f3ad4b3d3486e6439b164f06833ecded1d2db1e3d0f2b2e47aee9b347b is not running
Error response from daemon: Cannot kill container: 7a7c5782bc17: Container 7a7c5782bc179b974459565a096c4426cf67017ef19f700d74d3ba018689d253 is not running
Error response from daemon: Cannot kill container: 2213c11e69e9: Container 2213c11e69e94b986dec231ea4d4f0a2e61d90efc8781582db767b2046b354e1 is not running
Error response from daemon: Cannot kill container: 015b80a190bb: Container 015b80a190bbae35124e42624f1ea3e156a85a8960af433aa24022524f1c064d is not running
Error response from daemon: Cannot kill container: 4f0eacc51614: Container 4f0eacc51614e4f689a7085dfab6d2637f62f5bed647b2467334dad05904a9be is not running
Error response from daemon: Cannot kill container: 691cee374a41: Container 691cee374a41564c76fbfb9c99796295ada3def555c886d0592b3a53377ed9aa is not running
Error response from daemon: Cannot kill container: 8718e6dafd7a: Container 8718e6dafd7a9d6eff3675a06788be2e7f6e5eca07ea275de44b3917870b7036 is not running