GUI acceptance tests using environment deployed from packages.

Build: #2043 failed

Job: Multiprovider QoS storage was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
20 minutes
Revision
d4a37ebda8d9cad234b655aae75d29294552ebb5
Total tests
5
Successful since
#1990 ()

Tests

  • 5 tests in total
  • 19 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  37524      0 --:--:-- --:--:-- --:--:-- 37524
Error response from daemon: Cannot kill container: beb8e037fd8e: Container beb8e037fd8e9dc28b38098319d33ccbcfafb6abb019f4d6fc6628d5734fa1e0 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-CMQS/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQS/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQS/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQS/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQS/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQS/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-CMQS/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-CMQS/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-CMQS/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
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  41544      0 --:--:-- --:--:-- --:--:-- 41918
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 941263c1ae90: Container 941263c1ae903b245709eea2cb5ba12777dc1d8676dd31047afdc003e6761074 is not running
Error response from daemon: Cannot kill container: 3be8ddd7f92f: Container 3be8ddd7f92ffde752040617b2bc63a15542d5b53f939e6d213971b78a070aa6 is not running
Error response from daemon: Cannot kill container: ff91b00d110d: Container ff91b00d110de6e70a5b26933dd5815f807084435ce7ad88a53df052bf124da7 is not running
Error response from daemon: Cannot kill container: 27c4a95b7ee0: Container 27c4a95b7ee0650a45b7b483721546bd1d5256f8643084ccfe7d458340108931 is not running
Error response from daemon: Cannot kill container: 026b2dfad503: Container 026b2dfad5031de2e192caeefcc9c5d682b61bd63a4b2ebf3fccde02c1176e5c is not running
Error response from daemon: Cannot kill container: a3252dff0e4d: Container a3252dff0e4da28ad0c57cfbc74de6db18a9fd9a0b4f58b7e5c8333d320e35cb is not running
Error response from daemon: Cannot kill container: 39f138e47d20: Container 39f138e47d202c9fdd70c6a492ad4d2a9bac5926cc9443bb8478952252f5c4b2 is not running
Error response from daemon: Cannot kill container: 0632ef1b3310: Container 0632ef1b3310cef33e7fd09df03a0d13430b8b5ed8cbd5bfef0d57286c1db08f is not running
Error response from daemon: Cannot kill container: d664a7b8aa0d: Container d664a7b8aa0d7054100879269dcabbed642fa1923d3307f5f80274ad7c9ac65f is not running
Error response from daemon: Cannot kill container: 4359c4daaf29: Container 4359c4daaf297a76439762b160cbf1452c8fdedcd26ee444fd194a62ee3a8abd is not running
Error response from daemon: Cannot kill container: 5d69e650bc80: Container 5d69e650bc8073825959dc80c386e061f2bcfb09e448d6c14812b186e5aeee5d is not running
Error response from daemon: Cannot kill container: 2a16e69fb59d: Container 2a16e69fb59dc88e49ebed2b06ff496e9866ae042cffbae1760c558f12199dc8 is not running
Error response from daemon: Cannot kill container: 03345e0e2008: Container 03345e0e2008b03e0d43fbaf7ffcde588863916a80bfcbd36200427579c73fa3 is not running
Error response from daemon: Cannot kill container: 2af3a53b64e2: Container 2af3a53b64e2e7c445af3f18b8c53e0d7bed2a0141fcece24af89eb36e840c83 is not running
Error response from daemon: Cannot kill container: 0360f6005e60: Container 0360f6005e606a28fdf9190b8a935ae73921f6ac5a4462948d08c7827aa90007 is not running
Error response from daemon: Cannot kill container: 9b507b47b44e: Container 9b507b47b44e9cf1561ee631ab65c12bf4f949cbbe432ad097f37aa765266bb3 is not running
Error response from daemon: Cannot kill container: db51b3927525: Container db51b3927525db69d72e6e9cb3b14cfe1ad28b71e38e0f0f340b630b973d6ef8 is not running
Error response from daemon: Cannot kill container: 802490d62ccf: Container 802490d62ccf9c47c63d9f8c0b81af6bab2a60593a71368d0f3372bacad5ceb4 is not running
Error response from daemon: Cannot kill container: 2d53be0fbb94: Container 2d53be0fbb947ded454f1823fa7d171ce18732e82b02ad863fee4d696be51759 is not running