GUI acceptance tests using environment deployed from packages.

Build: #2142 failed

Job: Chrome onezone automations tests was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
36 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
Total tests
37
Successful since
#1998 ()

Configuration changes

Job Chrome onezone automations tests with key ODSRV-GAPT-COZATT no longer exists.

Tests

  • 37 tests in total
  • 35 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  46069      0 --:--:-- --:--:-- --:--:-- 46069
Error response from daemon: Cannot kill container: a4e02166aff1: Container a4e02166aff14c0ea15a52d937b175cc498baa2a2348d215926fe1a8ebd9c745 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-COZATT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/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-COZATT/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-COZATT/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-COZATT/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
W0518 11:47:08.296563     438 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  19069      0 --:--:-- --:--:-- --:--:-- 19069
Error response from daemon: Cannot kill container: 5d636739904a: Container 5d636739904aa0233e36808804791618d998c89dcd48287cf18fd12491057c6f is not running
Error response from daemon: Cannot kill container: 69d5e324b651: Container 69d5e324b651287d570f2363c553b393e2d8e6accbbf4d6494bcecb5e4ac51cb is not running
Error response from daemon: Cannot kill container: e96ee4987bac: Container e96ee4987bacea5381d604698701c54923080d93f8d588500699188ac4726f36 is not running
Error response from daemon: Cannot kill container: d7b0825b4aeb: Container d7b0825b4aeb4951c15170946a01f56cb04c1f4727609a2505f44f6e87e0ddfb is not running
Error response from daemon: Cannot kill container: 5b97a69d3f7a: Container 5b97a69d3f7a18e16997684de2b46f08b8466d80317fee00e0988c2caa408fee is not running
Error response from daemon: Cannot kill container: b9f96ec69563: Container b9f96ec695634f5d702433d73fd08ad77012d0cd058e51677203aa6a2da4cff1 is not running
Error response from daemon: Cannot kill container: a7062c82ec88: Container a7062c82ec8851ae97449a934296ccf58cdb741c0df7b60278c5b9ff9a176313 is not running
Error response from daemon: Cannot kill container: 324c5edd5edb: Container 324c5edd5edb11619ab1deeb9e96d33921ec2269a7372468380c9a40b3277c1d is not running
Error response from daemon: Cannot kill container: b021976af8d9: Container b021976af8d9bc074b823ee09ec6ea2c7521d42235646906791c7e13c68ceb9c is not running
Error response from daemon: Cannot kill container: 32b23a6f4365: Container 32b23a6f4365e426dd9e1256f1cdfb5ab7aadb37c8354fe05ace1ed12ec84fe5 is not running
Error response from daemon: Cannot kill container: c2fd35e5b96a: Container c2fd35e5b96a929428927e7d2cf2e0c0c5ce6010ce0fd990569dba5e916f6de9 is not running
Error response from daemon: Cannot kill container: e2a65e8aec16: Container e2a65e8aec160877ea9fcc72e0335e7e141570f113bc390caa7c4034a787cef0 is not running
Error response from daemon: Cannot kill container: a04f00c8d533: Container a04f00c8d533d59a72c2170593533512ad9c04b982a24770742b93f53d251284 is not running
Error response from daemon: Cannot kill container: 79ce4af859c2: Container 79ce4af859c2bd6df49d10815670474931e9d1aed8a40366d69a0ba2245c101a is not running
Error response from daemon: Cannot kill container: df34eae6dfcb: Container df34eae6dfcb2316eb7510bb61088df4f0e2115bee0f771e567dbf9e3a5bf01a is not running
Error response from daemon: Cannot kill container: a3c17edcfe54: Container a3c17edcfe547d1a59edb51c98a67a69dbe51990d74cfff4fa0436e2a4e2475c is not running