GUI acceptance tests using environment deployed from packages.

Build: #2128 failed

Job: Onezone invite tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
25 minutes
Revision
ac926e605a6b5528819b657cbc204091f50a9df5
Total tests
9
Successful since
#2082 ()

Tests

  • 9 tests in total
  • 24 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  47479      0 --:--:-- --:--:-- --:--:-- 47000
Error response from daemon: Cannot kill container: d4368b16df6d: Container d4368b16df6d3ce2a6d23d212f481b0922c281fe943c2c7db2159409aea34f38 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-COIT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/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-COIT/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-COIT/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-COIT/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
W0502 08:22:46.674958     495 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  48978      0 --:--:-- --:--:-- --:--:-- 48978
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: e6fc5c29aecc: Container e6fc5c29aecc8bdf29047f7593d91deec994bd16ce988c93dbf64762e18ee911 is not running
Error response from daemon: Cannot kill container: c6d1baaaa032: Container c6d1baaaa0324886fb35cc7869af1e3a99235e07ca41324d7fe501e62cfe6294 is not running
Error response from daemon: Cannot kill container: 476cedc47acd: Container 476cedc47acd29b2dc80ef09ba99ee2790bb44b9f63cf3b3fea82e8f9c1ab1f5 is not running
Error response from daemon: Cannot kill container: a87ab9b7d0ac: Container a87ab9b7d0acb0c1a613528fb79ab1ae6a57fc04212d0989d02fbdd611dfc8d3 is not running
Error response from daemon: Cannot kill container: 26f2467d1125: Container 26f2467d1125510144cfc97b8df571a9e55298a6d04f31586a823ca81aec7a45 is not running
Error response from daemon: Cannot kill container: 5a76527faef9: Container 5a76527faef913a1b170ad0f71a9466f8e2e5b226b7f5069b2eacd13ac9574bf is not running
Error response from daemon: Cannot kill container: 1a9920ff17a5: Container 1a9920ff17a586321dc4160ba8e85a98ec997ce5449cb3403750806c64521e8a is not running
Error response from daemon: Cannot kill container: bfce30c4e9b0: Container bfce30c4e9b049109e6a4291662af5002f8dd3e5bcec726da8f06b194bb531c9 is not running
Error response from daemon: Cannot kill container: 1b93f623db29: Container 1b93f623db2988a9689432d76bbdacc4ed07e4f6781d757950bf11ac23e02267 is not running
Error response from daemon: Cannot kill container: bbc738e2cbce: Container bbc738e2cbce59dfdfe535dc91ca09a22dad995da6a37bb2ca7b4266460b5b85 is not running
Error response from daemon: Cannot kill container: 6364965d1cec: Container 6364965d1cec8d5f9a5d06724fc3f61a6482b98d7d365a768cb03f7505994f38 is not running
Error response from daemon: Cannot kill container: 5fd4e952d3ad: Container 5fd4e952d3ad5be7e263f9e26f6082c0af729303f03da123173c09b97116ee3a is not running
Error response from daemon: Cannot kill container: 72015ff746a5: Container 72015ff746a50b3aa5e1a387a2aaed6ef2bf78b7e5b56170b66b0b85ad32aca0 is not running
Error response from daemon: Cannot kill container: 77874dd9d6b2: Container 77874dd9d6b2091ce56e69c3278d4fce0b299f109bae783fd71c43e2676d652c is not running
Error response from daemon: Cannot kill container: 7dbe75d47e96: Container 7dbe75d47e963a0c3ae353ce629403a52a6d93bc21cf55b9743a649a52d2a55c is not running
Error response from daemon: Cannot kill container: 85e519974235: Container 85e5199742358a7ff99cf3c02a4c7304050a2f2c89777331e83369a3b42017de is not running
Error response from daemon: Cannot kill container: 016d44592f69: Container 016d44592f6974cbfe720370553b2948e2fe5e5bd1d948935d39daac5eba93d9 is not running
Error response from daemon: Cannot kill container: 787aa5b11514: Container 787aa5b115144b07ad40c9f5d24494ff18e4152a4ac815f2bf80cf98f77dc1e9 is not running
Error response from daemon: Cannot kill container: acd7879a2645: Container acd7879a264560f430f85c2e5ba574f05009f25f4638f4dc93d22d5fcb57b3c2 is not running
Error response from daemon: Cannot kill container: 236398bd4a61: Container 236398bd4a6188156c6dbbde467ac1c9d190e7c263c9e86b1cf048600d7d1593 is not running