GUI acceptance tests using environment deployed from packages.

Build: #2146 was successful

Job: Oneprovider symlinks was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
23 minutes
Revision
55cdb7fe92fff892fdb8cf16f00c4ce6627a4c4a
Total tests
17
Successful since
#2129 ()

Tests

  • 17 tests in total
  • 3 tests were quarantined / skipped
  • 21 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  50576      0 --:--:-- --:--:-- --:--:-- 50576
Error response from daemon: Cannot kill container: ed577e183225: Container ed577e1832255ad61e51bdac6453dea418694b3564ad4a3b769a93125a062112 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-COSL/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/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-COSL/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-COSL/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-COSL/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
W0524 08:40:42.675226     435 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  46069      0 --:--:-- --:--:-- --:--:-- 45617
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 4c29b4fbaa3d: Container 4c29b4fbaa3dbbc4c047c0dd8ba798dd2ac23bd029557119c55e70b6bb84f3f8 is not running
Error response from daemon: Cannot kill container: b17ea0290cb3: Container b17ea0290cb30481ecc9b11e458af0115bb3da1e4f209bef3c9a035c63dac842 is not running
Error response from daemon: Cannot kill container: 15c5410f73d9: Container 15c5410f73d96784fb7b9a6d895d47621778b4369cd127d64f57e5f9610188da is not running
Error response from daemon: Cannot kill container: c300bff18992: Container c300bff189922c3aed69caf48e236088ac1455254da1c05f46eae18ce49b670b is not running
Error response from daemon: Cannot kill container: eb7e579a8038: Container eb7e579a8038ce275c599b04fece43e8a9611ecd8e00689ec56dda1ecaaf5b2f is not running
Error response from daemon: Cannot kill container: 5ba5a8e42630: Container 5ba5a8e42630d5f2d0f56606685ee76aaf563d9562119c31082437781718b331 is not running
Error response from daemon: Cannot kill container: dcb6c75989b1: Container dcb6c75989b19a56f0d27d4c9f019d79a8efe91abb043a52a5939aab5b95c557 is not running
Error response from daemon: Cannot kill container: bbe3b85220f8: Container bbe3b85220f84ff258c01d47d8366e24c2aea27a3288c36445d0f490871482a9 is not running
Error response from daemon: Cannot kill container: 36152e1da962: Container 36152e1da96230127e673a48bb1370eb4ddd159acdb7ebe552aa4dc3e689861c is not running
Error response from daemon: Cannot kill container: 5db5b72ad038: Container 5db5b72ad03874b811281b6227afb797a7191d64fd295fd3bcaf1d481397cbe4 is not running
Error response from daemon: Cannot kill container: 061b9b9ecb04: Container 061b9b9ecb04ad1de71ac0fc6d3c22717d8167adc6f97df27ad010a218102355 is not running
Error response from daemon: Cannot kill container: fa3c550ec661: Container fa3c550ec6615883e8a6fd2521865be8aea6a8af6e00d91181584f83e6c412f7 is not running
Error response from daemon: Cannot kill container: efa8fd20f07b: Container efa8fd20f07b2524cb48505f3bea970bad227ccdcca19b2b5623cf126367f6a5 is not running
Error response from daemon: Cannot kill container: 4b69a85b8ac6: Container 4b69a85b8ac600d19a7fdb4c5abe17add7e3ea2652bedeb2126fe6518adeac3e is not running
Error response from daemon: Cannot kill container: 1b08bcc94fec: Container 1b08bcc94fec6808275b0b09d1b7010d7a647ea54bb208e052bc19f6f58038eb is not running
Error response from daemon: Cannot kill container: 8725e3589da1: Container 8725e3589da1e67f5a81779c6572b88565589a642de43ae783a873ac9ba2e939 is not running