GUI acceptance tests using environment deployed from packages.

Build: #2192 failed

Job: Onezone harvesters index was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
16 minutes
Revision
466b4a1341ba42e3ce27e138642da6627c86d0c6
Total tests
5
Successful since
#2190 ()

Tests

  • 5 tests in total
  • 14 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  48978      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: 5e40d798aa7c: Container 5e40d798aa7c95d03ea014aef0181e35455d7bcc22c463363b527c5b775f7bc5 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
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
W0630 23:17:24.204766     455 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  41918      0 --:--:-- --:--:-- --:--:-- 41918
Error response from daemon: Cannot kill container: ddaf474c85fc: Container ddaf474c85fc0d01434ff840d7be5bc75f8b06c26a16f685c3297468261e3699 is not running
Error response from daemon: Cannot kill container: a6a4551ac53e: Container a6a4551ac53e9e63c96463e71d4c85131cf305ef2c8af008449469f452003d31 is not running
Error response from daemon: Cannot kill container: a74af106a0c7: Container a74af106a0c765dce3056432c40d1b928561b430124e9a4038911f2c230632db is not running
Error response from daemon: Cannot kill container: 8fdb7056cd57: Container 8fdb7056cd5721c766e058123309d483cfb48520b13692b645e947b81dfa3a84 is not running
Error response from daemon: Cannot kill container: d9a504e43b1f: Container d9a504e43b1fddce81df5a2eb0ff2058a9329fc7b7b5967f02ae10e9bde3b8c3 is not running
Error response from daemon: Cannot kill container: cb93b8cd8f36: Container cb93b8cd8f36b58fa89fb4496c861a4c6f8c4d73efebb6a15cbcc84d5c1b4523 is not running
Error response from daemon: Cannot kill container: c3f1c2b2a014: Container c3f1c2b2a0141cd04e75040398505a58a7c29d513e4e128fea2fd5cf94410fd3 is not running
Error response from daemon: Cannot kill container: 290f1e5c12ad: Container 290f1e5c12ade8d0450569cfbf458ae6a914d29abde0b975e33449e1e37b4e0d is not running
Error response from daemon: Cannot kill container: b3a2d310bd55: Container b3a2d310bd55b1af3f13f5d02340fdc7ffd4fe489a90d144927d196a9218e49f is not running
Error response from daemon: Cannot kill container: cf5f7315eb9b: Container cf5f7315eb9b9c9abace36512127e4ff0d10a1ed17861d710487adb76883e305 is not running
Error response from daemon: Cannot kill container: 9d4beccea077: Container 9d4beccea077aaa8f48ee3ddbe056d536a9f09585025043e335f74eb59c36697 is not running
Error response from daemon: Cannot kill container: 5d33fccf0020: Container 5d33fccf00207c14d3c8be36b46dd34e9bcf22ef98655fa8567c465f4cab6345 is not running
Error response from daemon: Cannot kill container: 64b8e6c61e09: Container 64b8e6c61e09ba02d67dc2b2e42ecaf406f0938016c11b14db080fa06f5d6c7f is not running
Error response from daemon: Cannot kill container: bd822ec1524a: Container bd822ec1524a13757bab0b07fbb46d567a8d8b94ef2d2548b1ea4fbc1e9eb8db is not running
Error response from daemon: Cannot kill container: 1725c084453c: Container 1725c084453cf3d0f5dddc48ddd7688059db562a6fa4450a1903705f150516cb is not running
Error response from daemon: Cannot kill container: 40e84aff92e4: Container 40e84aff92e43d57eabac604d8ff0743e0ce98f4d1fef9c6a895019c97b5ce7a is not running