GUI acceptance tests using environment deployed from packages.

Build: #2283 failed

Job: Oneprovider ACL files was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
12 minutes
Revision
8bf7c9f6df4b77754518d5d91f1bda1a458ce27e
Total tests
8
First to pass since
#2282 (Child of ODSRV-OZP-1780)

Tests

  • 8 tests in total
  • 11 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  50032      0 --:--:-- --:--:-- --:--:-- 50032
Error response from daemon: Cannot kill container: 21029a8d435f: Container 21029a8d435f9ab7358c4a99d1eb846c6c106d5ef5e425921c91cc6ee26de4a4 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-COAF/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/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-COAF/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-COAF/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-COAF/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
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]
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
W0826 23:20:30.361737     449 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  48978      0 --:--:-- --:--:-- --:--:-- 48468
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 772ae9f25589: Container 772ae9f25589195017fabf62d5e7b285c71f06c67b2da5c1b16654989b16b925 is not running
Error response from daemon: Cannot kill container: 3226ead59396: Container 3226ead593968564fc5681f888a177727674ac9fc31e27429fa0aa24554a6ac6 is not running
Error response from daemon: Cannot kill container: 47a2f92f12e0: Container 47a2f92f12e0dc85f1e20328f43c7d09b5ce98da134d8abafb606e55744338d4 is not running
Error response from daemon: Cannot kill container: e1fba8946e28: Container e1fba8946e28ec5242547dd432f50a781fac641f09020536958f72c171c22c00 is not running
Error response from daemon: Cannot kill container: dcdae1918ead: Container dcdae1918ead7f29d4ea64de49ffe1b3b10eddd26edb7db5fba8fa0e8169044b is not running
Error response from daemon: Cannot kill container: b3a0dd99def1: Container b3a0dd99def18437e2ef474b09ff0caab9e7578be7705092e8d8edd66a5dff18 is not running
Error response from daemon: Cannot kill container: 9405ab49dad7: Container 9405ab49dad774215fa8a2515e1a65da1e5b9709bc3a2579f8065f08a28e4670 is not running
Error response from daemon: Cannot kill container: 6b1cd9400ece: Container 6b1cd9400ece3db11df7461c61544a51f811e74e519afe7f88870c60e866e312 is not running
Error response from daemon: Cannot kill container: 2c58c8089dab: Container 2c58c8089dab473548dc93cd4f1348c8cf6293bb00ecb1a84a5919316269995c is not running
Error response from daemon: Cannot kill container: 5abaf47506d1: Container 5abaf47506d19e405475cb04b436bfc6868dd64956c9299ad05a28c36a6443ed is not running
Error response from daemon: Cannot kill container: 8e67e830c20a: Container 8e67e830c20aec0d67972deb47628af433881f70465dfbb242bbc36119da8d5e is not running
Error response from daemon: Cannot kill container: 56cfc50ec0f1: Container 56cfc50ec0f1023e60b7a87943fcd09ed2af314bbe4b330de14aed8eb6aa33e2 is not running
Error response from daemon: Cannot kill container: c6aa8b2d73e1: Container c6aa8b2d73e19b84184ca1898888df678c4319bce91bb4100390223d2bdec464 is not running
Error response from daemon: Cannot kill container: 44f08f501eed: Container 44f08f501eed56aac111b288e75a761982f610c04cf35fa6d2bca717bda6275b is not running
Error response from daemon: Cannot kill container: 527e2e4eb6b2: Container 527e2e4eb6b2534e90fd4ac6133f479b1cc62e9440be88e49f6587057ff59beb is not running
Error response from daemon: Cannot kill container: 1b8c94e68068: Container 1b8c94e68068649c801a1954ccdff2cdf37a511fafb02f97f4efbfa07191cb89 is not running