GUI acceptance tests using environment deployed from packages.

Build: #2193 failed

Job: Oneprovider ACL basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
13 minutes
Revision
466b4a1341ba42e3ce27e138642da6627c86d0c6
Total tests
9
Successful since
#2113 ()

Tests

  • 9 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  48468      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: 051aec6010ec: Container 051aec6010ec7f2ce0919148ff3045ef148ae5b87977e7aa008d1f8756cad784 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-COAB/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAB/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAB/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAB/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAB/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAB/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-COAB/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-COAB/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-COAB/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
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
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
W0701 01:03:27.773907     447 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  47969      0 --:--:-- --:--:-- --:--:-- 47969
Error response from daemon: Cannot kill container: 586587e134f2: Container 586587e134f2050f8070c5609a8ebe5cad34fc4894e815c7d7f323740a8db637 is not running
Error response from daemon: Cannot kill container: c475302f9101: Container c475302f910173889c9124534fbbcd7ab4932492d49434cc6e3ff59198f08438 is not running
Error response from daemon: Cannot kill container: 6286f890c78b: Container 6286f890c78bcc5225c1a6ee68555e44d7a41e32fd81e058cd43c491f7b1a11f is not running
Error response from daemon: Cannot kill container: 29864bddbe50: Container 29864bddbe508f5d39f4a15de805cc92e60547fd97e88dc7713775b39e074870 is not running
Error response from daemon: Cannot kill container: 1ed8641e4bf4: Container 1ed8641e4bf440c3a0e1a5f1a0c032a9366ab518c0130aca67fa1fd5448b4e35 is not running
Error response from daemon: Cannot kill container: 4765e3af34b2: Container 4765e3af34b24f11dc284a59873d32789a5a50db2eb50d434b83975c940f92e6 is not running
Error response from daemon: Cannot kill container: 38a6e61d41fd: Container 38a6e61d41fdc55050feea33f48b992153ecae1fbd9f301ef9d4ffbdcbc55e87 is not running
Error response from daemon: Cannot kill container: 13aa7785bef1: Container 13aa7785bef11ebb58c7c1eba35149369dca653092be9344943af412096ded52 is not running
Error response from daemon: Cannot kill container: d4745c69aad4: Container d4745c69aad4401e5abd7d39ec1a84664559b8ac16fe3a4874bfcfb66c0aa8e6 is not running
Error response from daemon: Cannot kill container: 118a10843753: Container 118a1084375360a1c9e62957108978eddcd00ba69497d22ef0749f49c8550465 is not running
Error response from daemon: Cannot kill container: ceb4203b6964: Container ceb4203b69645c083cb890b49598f1c8eac733b9b78d6989a2ea16e34a9db484 is not running
Error response from daemon: Cannot kill container: 9ea42ab8e357: Container 9ea42ab8e3575b7ecd088f2bf89dab79afae9e674445df43fa9799f7ee4ece66 is not running
Error response from daemon: Cannot kill container: b0b05b42c349: Container b0b05b42c349bfe2b55d3e75bd92fbf2bd4add410735e3fe50e5ac9101eac6e5 is not running
Error response from daemon: Cannot kill container: 5831374f492f: Container 5831374f492ff4921e546eceac80f2169bc5c81310e2fd7444278fd4401299e0 is not running
Error response from daemon: Cannot kill container: a42461049905: Container a42461049905df3be07ea1dce81d997400ba3833f6d32629962e662947cb0ca2 is not running
Error response from daemon: Cannot kill container: 6fd6f2b42c1a: Container 6fd6f2b42c1ad5ea98cf9eaf6a0a41db82a6f00efecab4a970d364eed6c7cfa2 is not running