GUI acceptance tests using environment deployed from packages.

Build: #2010 was successful

Job: Onezone invite tokens with caveats was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
10 minutes
Revision
ed4f134a7d934cf4803abda141850366f8511cb2
Total tests
4
Successful since
#1958 ()

Tests

  • 4 tests in total
  • 9 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  23149      0 --:--:-- --:--:-- --:--:-- 23149
Error response from daemon: Cannot kill container: e8537765b1b7: Container e8537765b1b79079915a932d8847ae5ac09d871309c8250589394d4107ba66f1 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]
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]
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
W0304 01:21:19.955545     495 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  45617      0 --:--:-- --:--:-- --:--:-- 45617
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: eb70c97d67f9: Container eb70c97d67f93fcd90ed24208b12ed01dfd290c9d71ee13d892327bab25e911a is not running
Error response from daemon: Cannot kill container: ab71c80eb0a7: Container ab71c80eb0a78caabc5613a53591f98730b3b9ea07c887eeb1563664d25ef32c is not running
Error response from daemon: Cannot kill container: 554df08780ea: Container 554df08780ea44ae85f86ff922d0d5f7c6853dca69d4f8b75cb4867357b350e8 is not running
Error response from daemon: Cannot kill container: 254e9aef05b1: Container 254e9aef05b1645e7abf954778eba3cdb7b6573adb7dbc95b3895082dbbd604d is not running
Error response from daemon: Cannot kill container: 971cd97e0b56: Container 971cd97e0b560afc5f2584ca549a5254581966d328b9964378988f6970d9f669 is not running
Error response from daemon: Cannot kill container: 04d0029a978a: Container 04d0029a978aa44b67aedc566a4286f7c5884853155ff261f34707ec9aeb2f9e is not running
Error response from daemon: Cannot kill container: 78dd7511eb74: Container 78dd7511eb742144b730ae4686daaf1462a69224d38e6fd6e5b21a05c83ec13b is not running
Error response from daemon: Cannot kill container: c4bf14a7769d: Container c4bf14a7769d214eed25bd238e2cee0dce7a53ab058cf14f7a3ccb498c64f94f is not running
Error response from daemon: Cannot kill container: f2d8037ddc73: Container f2d8037ddc734aa39c75a42f2169491de9cfa924a7125a605683c4f77bf23b9f is not running
Error response from daemon: Cannot kill container: 1153f92bd96c: Container 1153f92bd96cf388596567b80dbb1a434fa3bf41d9a3d20ee3fc5f8d42988811 is not running
Error response from daemon: Cannot kill container: e15a2a44d9ee: Container e15a2a44d9ee9316bb90908e5e0b99ab97ca812b62f1f374c654dc191e29246a is not running
Error response from daemon: Cannot kill container: f86109433ea7: Container f86109433ea7ec831d8d28e2095f0e899ed0f8d9a860a4778aad416f51394f18 is not running
Error response from daemon: Cannot kill container: fed311f10f97: Container fed311f10f97737590c0ba5ace5dc903329e5219b65f5c0c27f4126c28ed8c18 is not running
Error response from daemon: Cannot kill container: 2e0b6e331a43: Container 2e0b6e331a4326524d3c63f2546ad3ec1c002fd30322533a3ea9ce51358b6ec5 is not running
Error response from daemon: Cannot kill container: 1a89675b092e: Container 1a89675b092e32f631f6a5e2aa642fd7e784316a4ca67e2ec660e2b9593a53a9 is not running
Error response from daemon: Cannot kill container: 28b6bae5d9b6: Container 28b6bae5d9b66923cc09bd8865f68370591994a9db2fad8c49b3f14544ff45bf is not running
Error response from daemon: Cannot kill container: 96e82208559f: Container 96e82208559f5cd7bb394f0cf2aee9534bcd8e1eb5aad2853efdbc0145c627c0 is not running
Error response from daemon: Cannot kill container: baebc6a13382: Container baebc6a133822993074ba3458ac52d8490c9bfbc07012b75e19de31672c376f9 is not running
Error response from daemon: Cannot kill container: d8dcf8d838f0: Container d8dcf8d838f0430a46fb03aea0ab12b00f3434f13861c2a854fd1f0b218f7238 is not running
Error response from daemon: Cannot kill container: 0ea7e947ea76: Container 0ea7e947ea76f119f8c2112ee9b092efe635cf55945a41cdd76dd5170765e335 is not running