GUI acceptance tests using environment deployed from packages.

Build: #2022 failed

Job: Onezone tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
14 minutes
Revision
10ddb4213486b44781d6de3e618016ef93cedab5
Total tests
8
Successful since
#1943 ()

Tests

  • 8 tests in total
  • 13 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  44740      0 --:--:-- --:--:-- --:--:-- 44740
Error response from daemon: Cannot kill container: 1dd0ea5e4a79: Container 1dd0ea5e4a79ea765008aef1c7773d2080c23b3ab8534a8793e80018be9ddbd3 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-COTT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/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-COTT/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-COTT/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-COTT/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Unable to find image 'onedata/acceptance_gui:v8' locally
v8: Pulling from onedata/acceptance_gui
a1298f4ce990: Already exists
04a3282d9c4b: Already exists
9b0d3db6dc03: Already exists
8269c605f3f1: Already exists
c810ae7364ef: Already exists
78d356e6ec21: Already exists
792b20546d07: Already exists
c1d3130a77b3: Already exists
0c7ad6b015da: Already exists
114ec36e4007: Already exists
2bc588dde0c7: Already exists
89641d7ca7e2: Already exists
b6cd4b44aa19: Already exists
e1c77802a505: Already exists
f373aa611054: Already exists
Digest: sha256:97e4de524ef380ad8c07bf6c71280c378a5e0179834942ff0e6c0007d32b148c
Status: Downloaded newer image for onedata/acceptance_gui:v8
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
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
W0314 16:57:27.564120     494 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  42300      0 --:--:-- --:--:-- --:--:-- 41918
Error response from daemon: Cannot kill container: f58246facebc: Container f58246facebc815962c6342161e0588682392e29e880649caf3147000dfd6b16 is not running
Error response from daemon: Cannot kill container: 32e952287290: Container 32e952287290b4212b5eb00d24f0513551fe63c7014e2ebc3865be3fbeebf84c is not running
Error response from daemon: Cannot kill container: 7ed6a832868f: Container 7ed6a832868fd2c936dcd681d8f29210c9d0ce13a304ec73c355c2f3097ffe31 is not running
Error response from daemon: Cannot kill container: 584da6a4f57f: Container 584da6a4f57fa6c93406a25238c67ffad3333d08438fe4925f1153684f69add3 is not running
Error response from daemon: Cannot kill container: 76a99954fd9e: Container 76a99954fd9ee62e79c0cd1b642087fc336dcfc961aaea8ac44fc5ef2ab45d05 is not running
Error response from daemon: Cannot kill container: d56645eafc97: Container d56645eafc97a378ce2631da6f982ad589ca56b3922daff57176568d9c2f4e80 is not running
Error response from daemon: Cannot kill container: 393c8d2dbf6d: Container 393c8d2dbf6da89633654588dad7c8a456742d1798ce54e5fe21805f404b21b5 is not running
Error response from daemon: Cannot kill container: 6be625564673: Container 6be625564673bf9290314c02ae73d79452464c7fc8c338df15a77b353b8efeaa is not running
Error response from daemon: Cannot kill container: e00ef9d01981: Container e00ef9d01981e5505b53d6bee82876eddd2238fe44fb460d8bc11192528a6647 is not running
Error response from daemon: Cannot kill container: ab28fd0ce099: Container ab28fd0ce0996f64bf848afdc131808ed127fabef54ca40064c341e9463883ce is not running
Error response from daemon: Cannot kill container: 67ff595a733a: Container 67ff595a733af1b782040ab360f47c76b5b0cf99d8af8942463c9daafe088f0d is not running
Error response from daemon: Cannot kill container: 78cd5cdc6982: Container 78cd5cdc69826da28136de8e67b50ffc87ed69a007161b68bca41f7576338301 is not running
Error response from daemon: Cannot kill container: 3611eff7fdd9: Container 3611eff7fdd9e874426c4eca327087fd5d269f243f9dfd162ceec8f9b731f559 is not running
Error response from daemon: Cannot kill container: a9818f1730ae: Container a9818f1730ae42c8093551e9cccf62bbccb9890b4eaad2ed02c6c160829b0194 is not running
Error response from daemon: Cannot kill container: 7214aee0e583: Container 7214aee0e583ac436f43eaab7f6454c80b55e8cc17190f018fc1bc144ee87612 is not running
Error response from daemon: Cannot kill container: 392bff99df8a: Container 392bff99df8a80fa5acd7fa372f9a25f2fc4ec0f7f070a32450589d28b0220c5 is not running
Error response from daemon: Cannot kill container: 6441ea3cf968: Container 6441ea3cf968c58091187c6a9f9bb30da3f14353f511ae52fd319a3b1030a87e is not running
Error response from daemon: Cannot kill container: d0b34e8a3338: Container d0b34e8a3338f934d36febff3e23363f0dd42a42b2c3b87ff8eb58531679822f is not running
Error response from daemon: Cannot kill container: 2ea9ef0f5ba7: Container 2ea9ef0f5ba70a0ab8da72a5255a93a19159855708782f6fd46bbac1f7aa1452 is not running
Error response from daemon: Cannot kill container: 5b165ff4acc1: Container 5b165ff4acc14375005420e2a575931f289f41c2fb9a2bf366a909adcf5e5dcd is not running