GUI acceptance tests using environment deployed from packages.

Build: #2096 failed

Job: Onezone invite tokens with caveats was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
10 minutes
Revision
55bf187d0d4ebfece7f274afc16ccd4ba4d3d0b1
Total tests
4
Successful since
#1958 ()

Tests

  • 4 tests in total
  • 9 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  38139      0 --:--:-- --:--:-- --:--:-- 38139
Error response from daemon: Cannot kill container: 006dc80692cb: Container 006dc80692cb7f7f4835b4c82bf8b55e346c4bc2903ff587473c9331b5f7027d 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-COITWC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/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-COITWC/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-COITWC/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-COITWC/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
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]
W0412 09:44:09.370034     491 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  45174      0 --:--:-- --:--:-- --:--:-- 45174
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 12682dfb6b99: Container 12682dfb6b99188c63c139ac8bea11d05d20d27e89995a78023d8103477e64ac is not running
Error response from daemon: Cannot kill container: ad01e44ea483: Container ad01e44ea483d7573a8232c4f1a16478d3ea13a934b0961c3c5af2e126efe3cf is not running
Error response from daemon: Cannot kill container: 19653bedca91: Container 19653bedca91a82859316e245b09c4730087a893930be5858813c0c9f10f867f is not running
Error response from daemon: Cannot kill container: bb1165ced0b2: Container bb1165ced0b2e1482286fe8bb031586c42fcdef22b8b9093dd6dc7a8f5618373 is not running
Error response from daemon: Cannot kill container: 10f7da51fd44: Container 10f7da51fd4445f52b5db0573bbf30c101e06a51ba2e184e81d599c1578ea196 is not running
Error response from daemon: Cannot kill container: 12133ef64ca1: Container 12133ef64ca1c4144207641b294980fecefbe91b215fd6a108734452bf46d121 is not running
Error response from daemon: Cannot kill container: 204b283f646c: Container 204b283f646c0537f529efcb68648201303c0669109d8cb860cc6f1ce93f5995 is not running
Error response from daemon: Cannot kill container: 6cf871b96aaf: Container 6cf871b96aafe96c40cf0766d6141ce04cb319dabdebba412dfc77d11b9c2d88 is not running
Error response from daemon: Cannot kill container: 3fe4d4bc8e89: Container 3fe4d4bc8e892674645706324dcb1da2a7dc819c86a7cbcc50a6cd6b2d7efebe is not running
Error response from daemon: Cannot kill container: 254c8fccb975: Container 254c8fccb975cb88ff6a9b94b4024afaed0aca172d36687604a12368d284d033 is not running
Error response from daemon: Cannot kill container: f2ffb5de6dd5: Container f2ffb5de6dd5594ad723ff75bc59e47715f04d54ba8a6edb1e22d41d6a4122d1 is not running
Error response from daemon: Cannot kill container: b39edae11028: Container b39edae11028f231ede53e06a1c67e2d4f2964c08000a6d6fa3655229cd7676c is not running
Error response from daemon: Cannot kill container: a490b0827c2c: Container a490b0827c2c85ed7faca72b676dd78c45dba6f699c73f73af8000b67155844a is not running
Error response from daemon: Cannot kill container: ab9427dda169: Container ab9427dda1694724fcbcf255aaabc0f4e9bf4d57212ededfc7d75bf7f42544d9 is not running
Error response from daemon: Cannot kill container: dd22f453a6d9: Container dd22f453a6d9967bd32c2a7c5aa073526b82da9eb7cda22456ffee6327034f09 is not running
Error response from daemon: Cannot kill container: ae931c5ab5c1: Container ae931c5ab5c1e9d33511f199f66e88c927236105ff6f8126bd25a2b374aa40d7 is not running
Error response from daemon: Cannot kill container: 10b17300c084: Container 10b17300c084ea4d7303882e7facd1eee25aade5f3988fec77ccdb844efea0cf is not running
Error response from daemon: Cannot kill container: 438507e5ddad: Container 438507e5ddad9313ca030d65310ed12f0b13d9a03f8b1508588e56b1e4f10b36 is not running
Error response from daemon: Cannot kill container: d8c4e505b175: Container d8c4e505b1757f4e1a0c86dee94635f4af66440c90acc83c6a369314a49f1e5d is not running
Error response from daemon: Cannot kill container: bf2235e633b7: Container bf2235e633b74caa351a4769b219501454b4af4255fd504de08a7dee448c336d is not running