GUI acceptance tests using environment deployed from packages.

Build: #2178 failed

Job: Onezone automations was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
31 minutes
Revision
8046c81cb26d07683c2acee37fe8f6bde9d9a654
Total tests
8
Successful since
#2152 ()

Tests

  • 8 tests in total
  • 30 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  44314      0 --:--:-- --:--:-- --:--:-- 44314
Error response from daemon: Cannot kill container: 6a291d45f51c: Container 6a291d45f51c9019bc2a286b02236acbfb9657e9ed66f012cdff82313721ac83 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-COAT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/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-COAT/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-COAT/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-COAT/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
W0620 10:46:00.135738     431 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  34466      0 --:--:-- --:--:-- --:--:-- 34466
Error response from daemon: Cannot kill container: 1dc9e3afed3f: Container 1dc9e3afed3f868852e63fe3fded0dc5bc8fe70745a487b73b241a955cdfb682 is not running
Error response from daemon: Cannot kill container: 8813a7fde2e6: Container 8813a7fde2e6711909260dcf35d029697f55c6bdcab6945704af4a8a8fbe69a2 is not running
Error response from daemon: Cannot kill container: 796618411d73: Container 796618411d73aba470e4186bb4eb59f95811d8280c42caa40b6c7be1bb90bfba is not running
Error response from daemon: Cannot kill container: b5ee2b9ba7ca: Container b5ee2b9ba7cad2f04f8e485801235adfe2acf567bc0b75591a26a0ad5d6bdd69 is not running
Error response from daemon: Cannot kill container: f7df41504c8f: Container f7df41504c8f193ff99a2dc25570e33e0beab5d3d417cc4db4acf8563c2b802e is not running
Error response from daemon: Cannot kill container: 8d137cb92948: Container 8d137cb92948e0ae08a0ba099b130b1c317c3cbf5d2a34c6ac923f0642fa5640 is not running
Error response from daemon: Cannot kill container: 3e5bb1a0fc49: Container 3e5bb1a0fc491bff29afd12ad912102b99a8d657afb9f93cb43607faa2a4684e is not running
Error response from daemon: Cannot kill container: b5b05c0dff28: Container b5b05c0dff28adaefeed3e14c1597bc3f446c80487d2eb841a5e55a01879137c is not running
Error response from daemon: Cannot kill container: ae1be2ff3837: Container ae1be2ff3837f52a6941617fd788ee82230db1cca629fe79a87f660596d17fe1 is not running
Error response from daemon: Cannot kill container: c9d6bfd7b685: Container c9d6bfd7b6854fbd51452b78c9f4ad35b2bc2b789e86bce7b0d8b6ef00ac2394 is not running
Error response from daemon: Cannot kill container: e9d395a50cdb: Container e9d395a50cdb0a63c7c676844577e98d22f1a02cfce9fbcbc4ae27df2d71e9bc is not running
Error response from daemon: Cannot kill container: 2266762ce702: Container 2266762ce702bd9fefa4e5ad18aa1cf3176e1ff94ac2bc34d810b4f3a47e2d98 is not running
Error response from daemon: Cannot kill container: 89ab20e4232d: Container 89ab20e4232de0061cb20b840c93a8cbad790a84040d8ec9cdd9170679f36f84 is not running
Error response from daemon: Cannot kill container: 7dc85102dd15: Container 7dc85102dd152c1027683790668f4315c34cd28030ed941a4b34707758eaaee1 is not running
Error response from daemon: Cannot kill container: 42fbae93f413: Container 42fbae93f413ede92b42725b0004131c2ac00fb1c03dee2aa3fd4552e372a4fe is not running
Error response from daemon: Cannot kill container: 2ea602be2e65: Container 2ea602be2e6516a87d38f6e8647e79427b5b663b2d2f8eb61d4c7fbc4201aa25 is not running