GUI acceptance tests using environment deployed from packages.

Build: #2205 failed

Job: Onezone invite tokens with consumer caveats was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
26 minutes
Revision
1fe3e42089bf1cc76fd057bfa36bd47351e44af9
Total tests
9
Successful since
#2201 ()

Tests

  • 9 tests in total
  • 25 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  49500      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: 1f0510c7c5be: Container 1f0510c7c5be9410f9a22efc75b0b96c7d647d020addb76a01bc90bfa02feb64 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
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
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
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
W0706 22:01:11.286586     517 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  40112      0 --:--:-- --:--:-- --:--:-- 40112
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: b372be139ce9: Container b372be139ce9675bc5edc5353ce4befcef7ebbc7caf06f770ca60ea71d33c7f4 is not running
Error response from daemon: Cannot kill container: 583fb6704c9e: Container 583fb6704c9e0ac4de451f04b45902438d60b5eed99acf2f978ad6badf4ed9b1 is not running
Error response from daemon: Cannot kill container: 4126817c46c7: Container 4126817c46c721909d5d55e52082cad50efc7573bbe5abcf78dee50b8794dab9 is not running
Error response from daemon: Cannot kill container: 97bff80a4559: Container 97bff80a4559439fcdc25762316b466bae4edbafeeac1fddb52fb8e7f1aeefe2 is not running
Error response from daemon: Cannot kill container: 7dd09b98dfae: Container 7dd09b98dfaeb40fcb5fb3bbd43d428d04944d199be0a1ad194268aa413a0929 is not running
Error response from daemon: Cannot kill container: 774680e5954e: Container 774680e5954e6f7a5e6182fbf4e9fe72c522b7f7b872e8e418c9b0b20d0ec771 is not running
Error response from daemon: Cannot kill container: 7f72e8925c28: Container 7f72e8925c282f6ba2133be9a44244212097608db1ff3a8b455704096d72d65f is not running
Error response from daemon: Cannot kill container: a9d261221195: Container a9d261221195ce820830e0c335e636ee6bef76bbbf6995a01e2fc414279f3566 is not running
Error response from daemon: Cannot kill container: eafe7bc5b90f: Container eafe7bc5b90f430731ea57bae839908cbb2dc781150d60f1e5938750b0b7d981 is not running
Error response from daemon: Cannot kill container: f772410ba625: Container f772410ba62594e6e5cf75826a396b1c781dc3bdb1f332dc1bd6606c6a381429 is not running
Error response from daemon: Cannot kill container: c06b6ce39ed2: Container c06b6ce39ed2cff15bdf2307be90f7807c761a203e78f57e75599633e5e95ac4 is not running
Error response from daemon: Cannot kill container: 432bb50c53bc: Container 432bb50c53bcaf01bd03336bb4dcfdc10b8ae0665205840db045cb314eb2ae7d is not running
Error response from daemon: Cannot kill container: 05dd5b22587f: Container 05dd5b22587f25400f90b6dca4e53df982a77544332125b828a374e55e7aebc3 is not running
Error response from daemon: Cannot kill container: a8e366c287c5: Container a8e366c287c59f9260e9d9a10d0b69248f708c14b4d74f6d07a2d193c7aad352 is not running
Error response from daemon: Cannot kill container: d7612eff460d: Container d7612eff460d08279bc54ce5963cea50dd2a7cf58add167110a3a1bea460a98e is not running
Error response from daemon: Cannot kill container: 1636da219e2b: Container 1636da219e2bdb81a929062f0c59305db828e011f33318ae4595d3b052341404 is not running
Error response from daemon: Cannot kill container: 9566aaeabbe2: Container 9566aaeabbe26931bcedfd9412a5f5ca71b5a91249a8483c0ed2bf7f7a19c740 is not running
Error response from daemon: Cannot kill container: 2ab0f3e3f2a7: Container 2ab0f3e3f2a7458b3b3aa20442e0406fcc936a0cd80eeaf307c3335d6e591fb1 is not running
Error response from daemon: Cannot kill container: bc5030b2d5d0: Container bc5030b2d5d05cb08eec2a95dc1c5f9903f50dc764bc78608f9ac3d94f6b080a is not running
Error response from daemon: Cannot kill container: f71d5b0c3504: Container f71d5b0c3504a7efe0d72ef2e3b107b8594f9b8a699c35a8bf470a64b23b4024 is not running