GUI acceptance tests using environment deployed from packages.

Build: #2236 failed

Job: Onezone invite tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
25 minutes
Revision
0211ba80f01c42f60a611d61795cbf5a0fa9dc0c
Total tests
9
Successful since
#2201 ()

Tests

  • 9 tests in total
  • 24 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  49500      0 --:--:-- --:--:-- --:--:-- 49500
Error response from daemon: Cannot kill container: f8d8bd484372: Container f8d8bd4843720e473624b4f4eaaca261d3a979d9c67875394ab2a63df5eb1d36 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-COIT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/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-COIT/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-COIT/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-COIT/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
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
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
W0720 20:44:45.878323     510 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  40460      0 --:--:-- --:--:-- --:--:-- 40460
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: bd75914487b9: Container bd75914487b9b6af6c5b67f142cc6a243e2d73e96f0441395f5bda554477c701 is not running
Error response from daemon: Cannot kill container: 534bd491b2d6: Container 534bd491b2d61226c3a39c0f502e0655daf5e91a88fe890773b68f14ed71af8e is not running
Error response from daemon: Cannot kill container: 276ce3b837d5: Container 276ce3b837d57a50803aeb7135ca9f0f2916354d2ec4d0cd650e246fba0c34ac is not running
Error response from daemon: Cannot kill container: f8ffb779d403: Container f8ffb779d403f42ff3029e16b6095847455801fd7ed2309d46ad115a7a82b4d7 is not running
Error response from daemon: Cannot kill container: 3f30d5f15534: Container 3f30d5f1553472955f3ef027dba2f3e36df97e41d07405fa20886b4a3cc351fb is not running
Error response from daemon: Cannot kill container: c262364b2856: Container c262364b28564597d3277379215c6063d0979e13838d8c00ce1318f51d50518e is not running
Error response from daemon: Cannot kill container: f3668a7d590c: Container f3668a7d590c77d84ae1ee7dc022dec06aeaba977c00ee73b9fcfa5b2c865eda is not running
Error response from daemon: Cannot kill container: c355dfaf6b68: Container c355dfaf6b684c8e2cf70ca6f1a2e8fad71927c6470ca2732c4b248322f5a460 is not running
Error response from daemon: Cannot kill container: bd8f80c33d85: Container bd8f80c33d85d46d2c4ed6f75f48790850d2555a57f635f641702b63af43d31f is not running
Error response from daemon: Cannot kill container: d195425660b4: Container d195425660b402af7a14c99bad3f94ca45ff63102bfce42e825b57ca8ea9c061 is not running
Error response from daemon: Cannot kill container: c66507921d4c: Container c66507921d4c3b5c8945630253dc884f6971f4843251446bcc95f7b6e9234572 is not running
Error response from daemon: Cannot kill container: 173a09f24948: Container 173a09f24948f09a8f987bc751b733d0ff6fe5c801d5b4557ff04ab4cdd41b66 is not running
Error response from daemon: Cannot kill container: 7b3b848126e3: Container 7b3b848126e3da54d6c3a9f34a6d72d27286954a0aa24ffbf3748bcfe3b7c4da is not running
Error response from daemon: Cannot kill container: 28dfe931c8d2: Container 28dfe931c8d2ab4334aea4efbaf3afa36df3d232957764fecb12dd55199ae541 is not running
Error response from daemon: Cannot kill container: ab05af87c1c5: Container ab05af87c1c503fdcf6d1c54d1e423abe127bb7e58273517a120115e8248ba77 is not running
Error response from daemon: Cannot kill container: ecb22a6b1a20: Container ecb22a6b1a2031a58de23715fa5e08eef224041cb2fefeb0830dc714545bb50b is not running
Error response from daemon: Cannot kill container: ab5defe34cd9: Container ab5defe34cd9ff9c2183d8170b72dcdfaac165a31e3d70225443b35ddff5539f is not running
Error response from daemon: Cannot kill container: bf7a5fbbf864: Container bf7a5fbbf8644cfd7a229e7e07b0028eeced5bd69e2f81ac02908de89143d295 is not running
Error response from daemon: Cannot kill container: df9d2b5908ee: Container df9d2b5908ee5b49993ae13f127e5a92ae1602ba1b37950b73c72591d1de69ef is not running
Error response from daemon: Cannot kill container: d6b81b57d5d4: Container d6b81b57d5d477dd3cff55acfb4cb91a0790e3b7fe9d4069c034542044a0ca51 is not running