GUI acceptance tests using environment deployed from packages.

Build: #2110 failed

Job: Onezone harvesters index was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
13 minutes
Revision
616ef003a0a36dc00e59f722ca7550385601e480
Total tests
5
Successful since
#2098 ()

Tests

  • 5 tests in total
  • 12 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  47969      0 --:--:-- --:--:-- --:--:-- 47969
Error response from daemon: Cannot kill container: 4dbb30c92725: Container 4dbb30c92725e4c2a14e5ef4bd3d4a6e7d4080d19cb19a9a262d8ad43efe7920 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
W0421 06:00:49.549871     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  17043      0 --:--:-- --:--:-- --:--:-- 17043
Error response from daemon: Cannot kill container: 2a14331b7a35: Container 2a14331b7a356ccdad4944b3d2fff3e0156d6c53a0a298dfd8e6ac504233161c is not running
Error response from daemon: Cannot kill container: 2161857747c7: Container 2161857747c7b3b7ea6c425bdbd88ade3d8c5b4be93de7031cabf4b695f6b4e3 is not running
Error response from daemon: Cannot kill container: 9a5205be710b: Container 9a5205be710b6ac82d1082d91ed0928c0fc03b59e862bc12b9c0c5ee18eadc4a is not running
Error response from daemon: Cannot kill container: bf7e7f9397b6: Container bf7e7f9397b6bb4f69e00dc3dcc0873530c7dba327544357281ae73f384f54e2 is not running
Error response from daemon: Cannot kill container: de844caa7b8f: Container de844caa7b8f9c563a90d30c2bc6435076252ec14d3631b875b2e33c7ab08d6c is not running
Error response from daemon: Cannot kill container: 755ed3a10d2f: Container 755ed3a10d2fda47f44d2453a380d48ed7844b9576993bfad4e8d6e0be007cba is not running
Error response from daemon: Cannot kill container: 35daf1fac865: Container 35daf1fac865e6332395d56713dd1b818d0f8f7f7013dc5219399cd204a72dfc is not running
Error response from daemon: Cannot kill container: 79ab66246460: Container 79ab66246460ab9534e4d80b07e089b493c71907d933ee572af52c75e9beffe7 is not running
Error response from daemon: Cannot kill container: 4ba1bdcba63e: Container 4ba1bdcba63e18ea31d4548e14cb484a4d80b80a968ac62ff5ca847d7f957652 is not running
Error response from daemon: Cannot kill container: c5694a5dae91: Container c5694a5dae911a77f5eebd98cb67f68da5d7427e9523e02ee3130bf72a93a644 is not running
Error response from daemon: Cannot kill container: 9062780e6a7b: Container 9062780e6a7b6bfe33ba6118571698e3af173a4b2b6ed738e37920c65c15a652 is not running
Error response from daemon: Cannot kill container: 99da9dca618c: Container 99da9dca618c44f2d35e56137b1e1f99fc147365c312ea2a06b7ef9e78e31805 is not running
Error response from daemon: Cannot kill container: 880a740a873c: Container 880a740a873c70faee563ffc7ab76a307c4cce18d262414c8f9e23784536c461 is not running
Error response from daemon: Cannot kill container: 4b8813e4986a: Container 4b8813e4986a5606d64ad045f32ee203b3c3065c98b6022843b852b592071423 is not running
Error response from daemon: Cannot kill container: 4ca743d26627: Container 4ca743d26627b2b9ac8d8e89dc507d0cf5fb989c0f99c50340f8fe10952b9e04 is not running
Error response from daemon: Cannot kill container: 775231f657fe: Container 775231f657fe509c5e8cec3908a90a9fc46861570594618d6ecbe37d6ea12e0f is not running