GUI acceptance tests using environment deployed from packages.

Build: #1987 failed

Job: Onezone invite tokens with caveats was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
10 minutes
Revision
178097c5f0b63cb324fc6fb80e8aba8582f6f142
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  49500      0 --:--:-- --:--:-- --:--:-- 49500
Error response from daemon: Cannot kill container: bc9394ab17e6: Container bc9394ab17e69628dc1994e070d02884299d721e21d01956752ffc7fc1151b23 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
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)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
W0219 20:16:41.262673     450 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  48468      0 --:--:-- --:--:-- --:--:-- 48468
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 25c8483f489a: Container 25c8483f489a10174e8566886221974e2e8c4835a90808cfe15bddf22a885da4 is not running
Error response from daemon: Cannot kill container: 5e34824b7964: Container 5e34824b79647848365f5fce935bce8976995059c67b2b518f6e4cea0ba820d1 is not running
Error response from daemon: Cannot kill container: e4a95c2dd195: Container e4a95c2dd19511c4ca8b399abb6c39d303e5291f996354f71e994b963b93635d is not running
Error response from daemon: Cannot kill container: d55eabfb7320: Container d55eabfb7320847ff8feb3401589f1a24361567fb7dc2d18309d840cf54b51c0 is not running
Error response from daemon: Cannot kill container: 2e3252a7f08f: Container 2e3252a7f08f4a81604390930ec577c1d4a5613bf14604f89a7a66458393ac91 is not running
Error response from daemon: Cannot kill container: 2c57d5829727: Container 2c57d5829727260169e0f6b1ddf04754339f5c081abf79667f3d13d424659598 is not running
Error response from daemon: Cannot kill container: d71613a38072: Container d71613a380725a7d6a16ac7065d72918fc6172555862fa2de741d30f89d8c6a3 is not running
Error response from daemon: Cannot kill container: fd78181fee35: Container fd78181fee3563af9526c474e95eadc27f9c2c0c5bbd16cbddb712c43f4f793c is not running
Error response from daemon: Cannot kill container: 58b971c180ae: Container 58b971c180ae03173799ce2a893df44a825646133bb08e12502b8c1b7bd273a3 is not running
Error response from daemon: Cannot kill container: c216074c8fbb: Container c216074c8fbb61522b4d2fdcd865fd9bc6814a40547750523cf3f8f5110d71fa is not running
Error response from daemon: Cannot kill container: 8b16437e66f4: Container 8b16437e66f4587bd7215e810e9929d0dd03d25ccb0a338d2626033e4823ed01 is not running
Error response from daemon: Cannot kill container: bcdaa4bfa512: Container bcdaa4bfa51238005c1d8ce179dc89a9f6b165112623d682f7c91b98f5dd587a is not running
Error response from daemon: Cannot kill container: 5045886a6fc7: Container 5045886a6fc7728a7810d0c5dbc1c524e0657e61795d3fa20ee96a6776f613b4 is not running
Error response from daemon: Cannot kill container: 01751e1f3205: Container 01751e1f320597cb8016a98c981eec2c1e78fe9612f39ae1476b6c041d16dac8 is not running
Error response from daemon: Cannot kill container: 30b4954e8b77: Container 30b4954e8b77b549e809904701604163f10e4b508227d1b3dc6bd12b4f22590b is not running
Error response from daemon: Cannot kill container: 2238b3d7122a: Container 2238b3d7122ad09669d56a4a767227ed9ddeb494d437fd6e0abe91b2c33e74ad is not running
Error response from daemon: Cannot kill container: 6f513176479c: Container 6f513176479cab90d3c4adad149a0c64afabc9a0d8ce34de33148d591ec8de57 is not running
Error response from daemon: Cannot kill container: fdfb0d9df861: Container fdfb0d9df86143865215962762ba1e1e62cab4bc33a7883d7cb316f95001c0d0 is not running
Error response from daemon: Cannot kill container: b4217f76a612: Container b4217f76a61299c0e4e40a37199ae7b3a4b5574f2ce14e2b1ed4dc95fb2223a5 is not running
Error response from daemon: Cannot kill container: 9318a45f803e: Container 9318a45f803ebf2f1ac7b30b1edde55f3a4b21e4f130fe7c92cc7a672aeeee7b is not running