GUI acceptance tests using environment deployed from packages.

Build: #2145 was successful

Job: Onezone harvesters index metadata was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
28 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
Total tests
7
Successful since
#2129 ()

Tests

  • 7 tests in total
  • 1 test was quarantined / skipped
  • 27 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  45617      0 --:--:-- --:--:-- --:--:-- 45617
Error response from daemon: Cannot kill container: fe028acf6751: Container fe028acf67510ed8cd039cf325501c0cbda48736c835ee00fecfe2d9b6c48573 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-COHIM/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHIM/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHIM/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHIM/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHIM/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHIM/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-COHIM/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-COHIM/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-COHIM/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]
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
W0523 12:42:22.908221     429 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  15356      0 --:--:-- --:--:-- --:--:-- 15356
Error response from daemon: Cannot kill container: ed67e6346fdb: Container ed67e6346fdb4857d1cd6eb225cf70d5e627c84fd983e7bc80c72a5bd966a5ea is not running
Error response from daemon: Cannot kill container: 63fdef8cb67b: Container 63fdef8cb67b26f0a46d52ecbd8a7b231b4d0f28e5d26216c9724519626a8cb3 is not running
Error response from daemon: Cannot kill container: 672c7684c976: Container 672c7684c97647f4d96fe194650e3851ad05daa0d431359b8c4063d77b2e8c5e is not running
Error response from daemon: Cannot kill container: 77a188c44697: Container 77a188c446979698e97a80240809bc03b02c491a10ae31c5535326a8b982e72b is not running
Error response from daemon: Cannot kill container: d0ef70674193: Container d0ef70674193482228d37245fc1384b54947a8bcd98807e210d08872ea9f5f5f is not running
Error response from daemon: Cannot kill container: 4133a66e0bcf: Container 4133a66e0bcf9a0a09e264e1e395da2b29529ec6ec9964a72fcb5816c4aa2d53 is not running
Error response from daemon: Cannot kill container: c806d9f72fd0: Container c806d9f72fd00eef5fb0ac0ad8bb27865c8ea2b991da7d5cb078aa9e8827b37a is not running
Error response from daemon: Cannot kill container: 7a177da1d7d0: Container 7a177da1d7d0d82625ae930a1929abb358955675a9f318e6c9d079893882d3a3 is not running
Error response from daemon: Cannot kill container: 96fafb813855: Container 96fafb813855536ab2a60e8bbe0643d10b855ae9ddf963d6a72b55cf702f7653 is not running
Error response from daemon: Cannot kill container: c8778e3eaa41: Container c8778e3eaa41bed9a882d4ac41055741c1b0a3386a4b23cb1ef88b785ad45b35 is not running
Error response from daemon: Cannot kill container: 768ceeffba2a: Container 768ceeffba2a3488e5ff7178ed531ad090b5ec6e20440a4935d3881603ed17ad is not running
Error response from daemon: Cannot kill container: f138584b141f: Container f138584b141f29ec4ed8da71175d40d1df5495e9eb652c6e1b9c7f1dfe638fb6 is not running
Error response from daemon: Cannot kill container: ada392e257e4: Container ada392e257e4f02731a89d8757458f18c595be1ed986e795b57bc76c03ea78ee is not running
Error response from daemon: Cannot kill container: f6320d3599c3: Container f6320d3599c35331e2eddf89657d490ec5543c923779d3cf08061d007fdcaab0 is not running
Error response from daemon: Cannot kill container: 9f21d1e6e15f: Container 9f21d1e6e15f3c5202078698c873deb0a949786b63fe3cd432eb727035fe145b is not running
Error response from daemon: Cannot kill container: 42da68c556bf: Container 42da68c556bffe621c6cf538a6c704e45d3a673e09f34c445d8ba3db71e4baff is not running