GUI acceptance tests using environment deployed from packages.

Build: #2145 was successful

Job: QoS basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
13 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
Total tests
9
Successful since
#1990 ()

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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  46530      0 --:--:-- --:--:-- --:--:-- 46069
Error response from daemon: Cannot kill container: 51c21f73b39d: Container 51c21f73b39d857ce1caf7959c5503b6755a5124ca966c070a1ae4ebaab6f654 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-CQB/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CQB/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CQB/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CQB/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CQB/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CQB/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-CQB/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-CQB/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-CQB/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  48468      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: e52f1fb6dc7a: Container e52f1fb6dc7aa59b6bad18d2ebcdd35a611efdf116b9e2deb3728567ad738e0b is not running
Error response from daemon: Cannot kill container: a6f46dcb940e: Container a6f46dcb940e545d2d663dabeb5044ba05824d25bea5cdb0eeccea982fac980e is not running
Error response from daemon: Cannot kill container: 0c824f58cb9b: Container 0c824f58cb9b1ca8593e0873040de56362ba11a1b397ddd1619fa2ed3b8a5e86 is not running
Error response from daemon: Cannot kill container: 20b295c21eb7: Container 20b295c21eb7739077d64cd68a1632f6e787a9dedee9833e54fdf8ae0b205fe0 is not running
Error response from daemon: Cannot kill container: f986dbe162f2: Container f986dbe162f2da17a3db52ab1cbd5abc695b68af4d72000a753d0bf3dcf444de is not running
Error response from daemon: Cannot kill container: 526ee8fcc6e1: Container 526ee8fcc6e1a7a9495a197a858235bd58332c0033ecafed481984a5513ada86 is not running
Error response from daemon: Cannot kill container: 3849b0937f06: Container 3849b0937f069a6a4e490f89491ce64d49750b8fcb42b1e3aae486bf64177446 is not running
Error response from daemon: Cannot kill container: fe2342b96379: Container fe2342b96379468af5998feaef6b3d0660d475953c75f507725614afe52e3ada is not running
Error response from daemon: Cannot kill container: 8f973e3e2e0f: Container 8f973e3e2e0fb2f50bf86145efee91155a7e4f48a84683affcef535f0b51a95a is not running
Error response from daemon: Cannot kill container: 782c33e3ddc2: Container 782c33e3ddc2745ae0979f728134e2f8b045e649a35b96da0f351d3c2aef8564 is not running
Error response from daemon: Cannot kill container: 62448455e1e8: Container 62448455e1e836ddc1ee6418fe5462f1064253e7c82b1dcbc658a112fd45dadb is not running
Error response from daemon: Cannot kill container: cf4ae1d72a5d: Container cf4ae1d72a5d6c0c8476bb959fb6a12432fc6e931948bc86c6062e1ecaa0e482 is not running
Error response from daemon: Cannot kill container: f4b1a33d15b7: Container f4b1a33d15b78358568069403343a6e1487e4b7ce25821384e65b6731f3f8bd4 is not running
Error response from daemon: Cannot kill container: 7c5992369fc0: Container 7c5992369fc0c32f138e1e79bd32d9cf4ffaccb4b58b59d191fdf2441f991a1e is not running
Error response from daemon: Cannot kill container: d437e29a1f08: Container d437e29a1f08b686ceebf8eb8d1c443727fe85f411412916b66caa9fb39da788 is not running
Error response from daemon: Cannot kill container: 977c90a2b852: Container 977c90a2b85227612e8f8b270b2b710b09aa68fa9d41d3e1c5add02d9d0e2270 is not running
Error response from daemon: Cannot kill container: dcb008cf1df1: Container dcb008cf1df1646b0218ff0ddbbe23fee954405d1111a51a57da5d3842168d40 is not running
Error response from daemon: Cannot kill container: eebf06088fd9: Container eebf06088fd9968329a0aac5ca3711c2aa6c88cd1dab683ecead9f71493dcb93 is not running
Error response from daemon: Cannot kill container: 1db7faf2e83a: Container 1db7faf2e83adcec54d09122a900e1a454e3896619e2595af54477403934e1ae is not running