GUI acceptance tests using environment deployed from packages.

Build: #2102 failed

Job: Oneprovider ACL directories privileges create was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
15 minutes
Revision
bd958fd39bf31d2a3f76d4e4471d41f2b042959f
Total tests
6
Successful since
#1958 ()

Tests

  • 6 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  47000      0 --:--:-- --:--:-- --:--:-- 47000
Error response from daemon: Cannot kill container: 1e50c0b38135: Container 1e50c0b3813580ceb3ba467e8289faf72d96f58cd8a2539c8b69fb07314fe644 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-COADPC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COADPC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COADPC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COADPC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COADPC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COADPC/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-COADPC/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-COADPC/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-COADPC/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
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
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]
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
W0414 12:57:29.972018     441 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  37829      0 --:--:-- --:--:-- --:--:-- 37829
Error response from daemon: Cannot kill container: 7e6f07266737: Container 7e6f0726673713db9e8cd542755dc1ad139c9aaccffcac9ba40ce6b2e2801be4 is not running
Error response from daemon: Cannot kill container: 04b75ab06374: Container 04b75ab063747bfb95ae5afcfb10422e7289d78c105628928c317456bcb4d7d3 is not running
Error response from daemon: Cannot kill container: 4f8ad9909dc9: Container 4f8ad9909dc9e40532af57b6294eee494df9f22f54f873b0e415aabae8502a04 is not running
Error response from daemon: Cannot kill container: 81d27d6adba7: Container 81d27d6adba75faf2c40c66b6917b32bd9d5cdaaf2f5d1be6471f5ddf6dd22f1 is not running
Error response from daemon: Cannot kill container: 48d645cb42f0: Container 48d645cb42f09c6597979d226d2407fb6c24e4277b800e3e7764e529ac0ff71e is not running
Error response from daemon: Cannot kill container: b98e54c69bd7: Container b98e54c69bd791b2efa9dfcb24c38e2b82c37e0a3d06fc67ea4af7360e6a3bc4 is not running
Error response from daemon: Cannot kill container: e6831f19cc63: Container e6831f19cc637ccf3e1bd9f64b408fdde9dda513cf97eae92a9a2069ee6f2b32 is not running
Error response from daemon: Cannot kill container: d1be932d4ded: Container d1be932d4deda4e8f6efb741f629610668da23ca7d31ee4242e92230bc1b30b0 is not running
Error response from daemon: Cannot kill container: a5972297747e: Container a5972297747e8223b1ac1a7d09fe217b0f637373e5f70b754226465b163c5ebe is not running
Error response from daemon: Cannot kill container: e579cdfb7d1c: Container e579cdfb7d1c1d1105bcec60ce8e89796e0844da111a3c27438780f1f023b51b is not running
Error response from daemon: Cannot kill container: fcefec7a38be: Container fcefec7a38bedeb25c113e9bdcf8d3e85c01233fcb71ff6012f466af68b425ea is not running
Error response from daemon: Cannot kill container: df8eda298b96: Container df8eda298b9687e921fc38d1f273e89e158ac775f6c00a5efd3a060c86ac4604 is not running
Error response from daemon: Cannot kill container: 6b29facf9214: Container 6b29facf92144a9362c367dd1814e6d9d703eea97e6c4c1044c5bfce3254cca3 is not running
Error response from daemon: Cannot kill container: d388936e98f4: Container d388936e98f4b5261c6acb65c6dde575e198ea594324176cf6277c35af8e76c2 is not running
Error response from daemon: Cannot kill container: 0d2dfe44f8e2: Container 0d2dfe44f8e2db6bac0f39dc47344d225ceeb676a819b9205b7224ab2677940f is not running
Error response from daemon: Cannot kill container: db451d0931b5: Container db451d0931b5ef74852191780d4be4aa9608740bd809340c6e163375e4ee70bb is not running