GUI acceptance tests using environment deployed from packages.

Build: #2140 failed

Job: Onezone harvesters index was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
14 minutes
Revision
dfd405a02fa2a4bab1ba6431bc2638a43a9cd1cb
Total tests
5
Successful since
#2098 ()

Tests

  • 5 tests in total
  • 13 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: b2f4e245d2c3: Container b2f4e245d2c3713a6c295b000b3e00039e5c41204b98596791785f1cc4fa5e56 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-COHI/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/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-COHI/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-COHI/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-COHI/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]
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
W0516 20:29:57.640031     434 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  48978      0 --:--:-- --:--:-- --:--:-- 49500
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: be06bf967c8f: Container be06bf967c8fdc09a67bc3c8055012a4e03c0319aeab9fd1ae62e87fee3785a5 is not running
Error response from daemon: Cannot kill container: fe343c6a5288: Container fe343c6a5288468a023f56584ef5271f90a6a59a19d660b7d3edab899990cd4d is not running
Error response from daemon: Cannot kill container: 300db5d4af2e: Container 300db5d4af2ecc92fdbcc96bfeff0e70f00065a09bfd10eee4a44798e888e338 is not running
Error response from daemon: Cannot kill container: dc01034ba184: Container dc01034ba1843ee22fb050537c90662d3e336a67bf7be9160d1cd342492071f1 is not running
Error response from daemon: Cannot kill container: 67a707858429: Container 67a7078584292c6e7c4c835eebebe7b727b7191fc305db123db3218754eae05f is not running
Error response from daemon: Cannot kill container: c0253636af3d: Container c0253636af3d7eb911e74fd498f9a566525e754a49baa795b080e101962a9092 is not running
Error response from daemon: Cannot kill container: 98200ac90112: Container 98200ac90112793a8aadb41c068cf765a5765517ec38d06f0aae2401f61015bb is not running
Error response from daemon: Cannot kill container: 04515f4e03c2: Container 04515f4e03c2232e13ab0f07d532ff69b6c7eafef5f4c0f00e40b5bf8595e98e is not running
Error response from daemon: Cannot kill container: 519364a817cb: Container 519364a817cb862023641902b6407a454ef9e0e4990795b5041fa47246778852 is not running
Error response from daemon: Cannot kill container: 3ca37e47014d: Container 3ca37e47014d01bdd27cd12bbd885e6d58291dbd48f12d767530a495b1639aee is not running
Error response from daemon: Cannot kill container: 6a14ea7a6878: Container 6a14ea7a6878aa76074a4f008dc6de744f11d85cdacf69cda0f25d7176b76fef is not running
Error response from daemon: Cannot kill container: a544848e5eaf: Container a544848e5eaf06ce5abcb506660d11a1b3a82cd6828695982d78940ea53a5f03 is not running
Error response from daemon: Cannot kill container: a0ee3a3f6134: Container a0ee3a3f6134298a35887ef2653192ac1ccae34bfe47c8ad9dcff119b40d0376 is not running
Error response from daemon: Cannot kill container: 8a2b6deda7cc: Container 8a2b6deda7cc2c744a3203e797e700c39c2467b30991762abcb6fbad385c7106 is not running
Error response from daemon: Cannot kill container: 72b571a47a54: Container 72b571a47a541290731cc432d86937f66fe512b540e9205d2202202fe324c5ae is not running
Error response from daemon: Cannot kill container: 510f931f4668: Container 510f931f4668ebbaa687f4ce6a5f89ceec46bf041e575f81cf1674f734d2c4f2 is not running