GUI acceptance tests using environment deployed from packages.

Build: #2024 failed

Job: Onezone invite tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
40 minutes
Revision
7b0177f002a795b08d7993ad38814ad4594f2bb5
Total tests
9
Successful since
#1969 ()

Tests

  • 9 tests in total
  • 39 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  23619      0 --:--:-- --:--:-- --:--:-- 23739
Error response from daemon: Cannot kill container: ffbabc28111d: Container ffbabc28111dd3831e94b6d2449672682fbd023da2160e91ece689d98dd3a87a 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
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)
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]
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
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
W0315 17:38:37.519364     496 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  19227      0 --:--:-- --:--:-- --:--:-- 19227
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: 3599bec7a19e: Container 3599bec7a19e7971b3d019623375c3bc40e4ffbda95b500c2d7e96b06666cd38 is not running
Error response from daemon: Cannot kill container: 60a182df01a9: Container 60a182df01a95115edec661340cf5bd5f0541e7849695bfc6f9df4e25fc2e71d is not running
Error response from daemon: Cannot kill container: 251a38d95550: Container 251a38d955507489d14947bab2ad830273cdaf9b9fd39d087391e8790346eb10 is not running
Error response from daemon: Cannot kill container: df467146f0d9: Container df467146f0d98cd9968655a6531ddc2a67693a15d09d777540f4968a6395b75d is not running
Error response from daemon: Cannot kill container: b78305d74498: Container b78305d744986ed1fb9fe3f6ff07dad45e9c7c74403f351a105a7ac724af823a is not running
Error response from daemon: Cannot kill container: c91457d11c56: Container c91457d11c56c8d6f02833cf0932b4a131fc1b0a242bcac302107e92a1afd775 is not running
Error response from daemon: Cannot kill container: d0a472b99aad: Container d0a472b99aad633b7bac00a7f7c8d5e1be655101995933c595caea58e5bb41f7 is not running
Error response from daemon: Cannot kill container: 662129f5f621: Container 662129f5f621e331bc07a8bdf6f5079fc3ce505cbe7313d9c287fd8d5da1f92f is not running
Error response from daemon: Cannot kill container: b37f1693619f: Container b37f1693619f252aa6b2bfba510225205579d8a69a3105e3b62ea88a91d24a16 is not running
Error response from daemon: Cannot kill container: 6e9e86f3e684: Container 6e9e86f3e684d9bc1fc05d300b8a6d6e53dd81c53ef33525290b37ac0baf5aa2 is not running
Error response from daemon: Cannot kill container: 260d4673321d: Container 260d4673321d03b50f845a5e34cc59d5ab85f079c22b747cc91e50ea9d1c6f69 is not running
Error response from daemon: Cannot kill container: f7e89423a5c7: Container f7e89423a5c7120b5c6456dec55c69abb30f5b92423cd8ddeb0c0be47dd79d65 is not running
Error response from daemon: Cannot kill container: 98e62e16e931: Container 98e62e16e931870a86083e7f389a4a70d5b5dd8b3d1210ee49a566d9ee3305e6 is not running
Error response from daemon: Cannot kill container: d4f03f8db439: Container d4f03f8db439d9cbc9cf302e44e9f822f223c1ab595758cf31819bd1c26fca1e is not running
Error response from daemon: Cannot kill container: c5564db0dc2b: Container c5564db0dc2bd60dea69ccf6bfd483d41876cb0bbb6aaab59e12615c79aaa8dc is not running
Error response from daemon: Cannot kill container: 95b08a0fbc00: Container 95b08a0fbc00ce56fb960a4c40a74dddb4311c4c2814b31e1c6f4fc50b9a2c80 is not running
Error response from daemon: Cannot kill container: 8b489edf7b0a: Container 8b489edf7b0a7a919925d9d142c2c703ceb93e156bfeec7b2bd7508e5b726be2 is not running
Error response from daemon: Cannot kill container: 2970055a8f34: Container 2970055a8f3418946fbe3747e0dec33c1bb68a1ce01e94d6aac2a3405684aa9f is not running
Error response from daemon: Cannot kill container: 25f89168f215: Container 25f89168f2150b3dda57130b1abeb665ff25217da0d50be687fac4189627d87c is not running
Error response from daemon: Cannot kill container: effb302e1ba8: Container effb302e1ba87118380b658301e81c190d489b0ef72e21b3b6c9dc8d971d6e50 is not running