GUI acceptance tests using environment deployed from packages.

Build: #2112 failed

Job: Oneprovider ACL directories privileges remove was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
19 minutes
Revision
d6888cd402c1e2c666417f7e0c3bb45e62d1469e
Total tests
10
Successful since
#2082 ()

Tests

  • 10 tests in total
  • 18 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  42688      0 --:--:-- --:--:-- --:--:-- 42688
Error response from daemon: Cannot kill container: 3fbb21a68f2e: Container 3fbb21a68f2e43ed66f00840ac2ef32d4f21d070b0024a1ae423a496272b44c9 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-COADPR/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COADPR/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COADPR/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COADPR/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COADPR/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COADPR/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-COADPR/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-COADPR/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-COADPR/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
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
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
W0421 09:24:18.927716     440 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  35250      0 --:--:-- --:--:-- --:--:-- 35250
Error response from daemon: Cannot kill container: 14e8c2903327: Container 14e8c2903327b97a87f154bbb05745166cecf6d250a3df73d96a1426589788e1 is not running
Error response from daemon: Cannot kill container: cb86051101f5: Container cb86051101f56cfcd3818994a8e07360b1f2355b4785772e6650cbc97bcaed8c is not running
Error response from daemon: Cannot kill container: 454bc07381fc: Container 454bc07381fc5df1f8179b0bda058943f875fd9e9710b608dbb2151aaac43cb2 is not running
Error response from daemon: Cannot kill container: 0cffc2d77b23: Container 0cffc2d77b23f13249a44360d7c13240f99920f443be201b489f75fffe45785b is not running
Error response from daemon: Cannot kill container: 510e9ad2a23d: Container 510e9ad2a23d9d5b9c9be0e514edfd9f8f63e28fcbfcf73f384a94d93e53bd50 is not running
Error response from daemon: Cannot kill container: ec02c3c9f5d7: Container ec02c3c9f5d780e43bd10b85980224d2b07e2bee6e2fa0a825c2c83566ff1723 is not running
Error response from daemon: Cannot kill container: e883141715d7: Container e883141715d7f59dadf83dcd8e79b37a6c8cc47bdc46d3a376397c6e01f001f3 is not running
Error response from daemon: Cannot kill container: d4907dc0dd14: Container d4907dc0dd1402ba7501226ad211313b1844e7713322bb09a091a9989fd858d6 is not running
Error response from daemon: Cannot kill container: d31a586c72cc: Container d31a586c72cc020ba052f7007b4067b316e739fa00094899a3ab41cd2f50836a is not running
Error response from daemon: Cannot kill container: fea63ef3d04c: Container fea63ef3d04cca399c74987413c07365bf840062b24dfe62a5013327e3f59a71 is not running
Error response from daemon: Cannot kill container: 907fee6d0b5f: Container 907fee6d0b5f58e47ef6e0b27662d7639a0d028a10f79820dbae6c5dbf97e34d is not running
Error response from daemon: Cannot kill container: 2f2bd3c7c44d: Container 2f2bd3c7c44d12bfdb236811ecb3c5d743786454e9da003023a44c74f6691fdd is not running
Error response from daemon: Cannot kill container: c851755b719e: Container c851755b719e8dc1a2d4866c5b95bcd1472c37555dae7bc124e1b6377dcc9e2e is not running
Error response from daemon: Cannot kill container: 3db0f47a5c60: Container 3db0f47a5c6053fa8db839b9b10683d3880a3bb2fad4c55e9e4aff4f11e3dcd4 is not running
Error response from daemon: Cannot kill container: d42bd978555b: Container d42bd978555bc8382170678e5a1f97dcb7d2ab231b8bb8e11d8795b78879657d is not running
Error response from daemon: Cannot kill container: 6f99d6dc2102: Container 6f99d6dc2102f64d036cfc23f8edc67a35c328186511fd495fad2ad9f781474b is not running