GUI acceptance tests using environment deployed from packages.

Build: #2145 was successful

Job: Onezone harvesters index was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
14 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
Total tests
5
Successful since
#2098 ()

Tests

  • 5 tests in total
  • 13 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  48978      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: 53a3ae34a525: Container 53a3ae34a5255820a0af667c20d8e07acc88a20a1b802100b5b9bcaffdcdd47c 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-COHI/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/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-COHI/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-COHI/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-COHI/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
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
W0523 12:50:26.222825     436 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  47969      0 --:--:-- --:--:-- --:--:-- 47969
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 860eb62d1f79: Container 860eb62d1f7965128869ce61e98501805d557023a04b4fd10428fb1aa1a31461 is not running
Error response from daemon: Cannot kill container: eaae53428d22: Container eaae53428d223a4f3472b2df013484b48e7f5a6722f5e7796b33cd1cbcc31eac is not running
Error response from daemon: Cannot kill container: dfcfee913b2c: Container dfcfee913b2c9053bb09ee7eea078db1f2986cf2debe5fe9cb9740896971fdba is not running
Error response from daemon: Cannot kill container: 749a66ace45e: Container 749a66ace45ee0863feb99e56defcf1b305f76051ce4b97f9519afb7eb7745c5 is not running
Error response from daemon: Cannot kill container: e3e5d2a5ff8d: Container e3e5d2a5ff8df2aeb0eabfea425d2e19ed7cc8edac917bb74e8135980690fe8c is not running
Error response from daemon: Cannot kill container: 12f8e99bd179: Container 12f8e99bd179e029c6816b865381af8fb2c0fc8b5586ee4fccc3c05e4f37b061 is not running
Error response from daemon: Cannot kill container: 9adc5050a5a6: Container 9adc5050a5a6e59647c4da6b433750954b56c3f30678419e77409ca95f00664b is not running
Error response from daemon: Cannot kill container: 63648433f785: Container 63648433f78509f2277a0a5194d85a2b83d2f529893db75b3cde3226fb4e0c29 is not running
Error response from daemon: Cannot kill container: 7d3176ebcf8f: Container 7d3176ebcf8f3c715c680e93581d2cb6279af63c7159bb4ec9435b32af8e8776 is not running
Error response from daemon: Cannot kill container: 71f28ca9c9fe: Container 71f28ca9c9fe734101dabf56f49408d8ba1bb870aa82fb38f71e542bd2b9f55b is not running
Error response from daemon: Cannot kill container: 96a3751f1f78: Container 96a3751f1f785b6ffe3d481c0edb201fb6bc9227c661f4143163eee6ab8731c3 is not running
Error response from daemon: Cannot kill container: e39aea0f17dc: Container e39aea0f17dc9025bfbe12cede90c2f6bda5e38d1fd9dc75684220ccc57381c7 is not running
Error response from daemon: Cannot kill container: 730d5541008f: Container 730d5541008f159f03ead06fcbaff154dafb3008849a4407c308692b7c0882d8 is not running
Error response from daemon: Cannot kill container: ab8fe1ab28fb: Container ab8fe1ab28fb9894076575a29a7eb32b5920b0a0a6ac7284189ad1bfb782b3c9 is not running
Error response from daemon: Cannot kill container: ccd89d7c2556: Container ccd89d7c2556144457fb36207c8729592a3570664b924b49102c8f52b9dd5800 is not running
Error response from daemon: Cannot kill container: a2a2479aec7c: Container a2a2479aec7cff83248df5b807ccdac855d7154c5594bb8046174dba576b2ab1 is not running