GUI acceptance tests using environment deployed from packages.

Build: #2107 failed

Job: Onezone harvesters index was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
13 minutes
Revision
616ef003a0a36dc00e59f722ca7550385601e480
Total tests
5
Successful since
#2098 ()

Tests

  • 5 tests in total
  • 12 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  37524      0 --:--:-- --:--:-- --:--:-- 37524
Error response from daemon: Cannot kill container: f7fe8de11222: Container f7fe8de1122257497e2e087567fe0dd8180623ed244c25458244dc7eba46d56f 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
W0419 08:46:44.670353     434 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 response from daemon: Cannot kill container: 4acf17c499de: Container 4acf17c499de9fa2bce46b112ee3c615115a079406d3a036e38c97e5ee3aef09 is not running
Error response from daemon: Cannot kill container: 87a62236a393: Container 87a62236a3938b0335446ee9dfbc0098c3f8ad78eea17e647ac2179ceaa13999 is not running
Error response from daemon: Cannot kill container: fee4bf802e58: Container fee4bf802e589bb86a71c8e4f123a6b8ec839bebb0220a7e5ab1c59492d6ac02 is not running
Error response from daemon: Cannot kill container: 0b11ca5baaf3: Container 0b11ca5baaf3f4e147dc4c8d6be12fc65474d4e57c8cd645b971df82ca8a4f28 is not running
Error response from daemon: Cannot kill container: 8c00ac238c2f: Container 8c00ac238c2ff8090baa568d3bf712f7915d49ab1db9f42380447540c3c240d8 is not running
Error response from daemon: Cannot kill container: b557ac99849f: Container b557ac99849fd0cee96f0d8658fd6d9392d9de27aec5132fa073ecc86ab6766f is not running
Error response from daemon: Cannot kill container: 224aa2dcd1c0: Container 224aa2dcd1c04d133d7b696445bb5690d9a413c21f1631333c98b971d4e4c7dc is not running
Error response from daemon: Cannot kill container: ee1fb75eb715: Container ee1fb75eb71513bdfebd6702a17c738fec1042df73ab299467638d728b09ad87 is not running
Error response from daemon: Cannot kill container: aba771dcdf83: Container aba771dcdf8323470dd7e380421fc62dbea5e7455e51a205a8cb3d216302ec58 is not running
Error response from daemon: Cannot kill container: 2dc64c54078f: Container 2dc64c54078f17d47ae0d65a7df4d7ef9661e12ec8407060d2605807e6401cae is not running
Error response from daemon: Cannot kill container: 5e83d229b8f1: Container 5e83d229b8f1d39f42243bb1e64ba222da6f3a5d0d23f944d732e2f6b5467859 is not running
Error response from daemon: Cannot kill container: bb6c80900d02: Container bb6c80900d02f5719d82de88d4150ef0d32925b6ce1381c6c059af858ea6873b is not running
Error response from daemon: Cannot kill container: e22f25f88ee1: Container e22f25f88ee188a06a4b4dbc24863dda763394c6dd23cc54b9b4faeaf0b60df0 is not running
Error response from daemon: Cannot kill container: 5e092bf9713c: Container 5e092bf9713cd599fcb0ba7656bbfb1fe0246c289a5dce2a4e1504889a6e6a02 is not running
Error response from daemon: Cannot kill container: 1c16b45ac337: Container 1c16b45ac337b81ddfad5ca0c52244c22e36b04a8127392c60c2740908cda169 is not running
Error response from daemon: Cannot kill container: 2dd3a0c13c76: Container 2dd3a0c13c76597d9104b732fa070bb580f6ae859bd8269a9be5ba1e5c2b66e4 is not running