GUI acceptance tests using environment deployed from packages.

Build: #2234 failed

Job: Onezone harvesters memberships privileges was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
14 minutes
Revision
0211ba80f01c42f60a611d61795cbf5a0fa9dc0c
Total tests
5
Successful since
#2201 ()

Tests

  • 5 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  48468      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: ba226147e200: Container ba226147e200b19532658584bde19179fd286a12b982f16a091ff679bc83e9b9 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-COHMP/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHMP/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHMP/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHMP/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHMP/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHMP/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-COHMP/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-COHMP/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-COHMP/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
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
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
W0719 20:44:55.543907     447 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-elasticsearch-0" not found
Error response from daemon: Cannot kill container: 4a6188066276: Container 4a6188066276e14a256b1203c2779f863efb2b87014c7164fb858d9fd6ce6249 is not running
Error response from daemon: Cannot kill container: dd6fceffee2d: Container dd6fceffee2d6e448450864be510f61fa29854c58641a267c471d3e9fab1e081 is not running
Error response from daemon: Cannot kill container: 366a4d08dff4: Container 366a4d08dff4ea8031032645f1d73d986f28108ed7acd951fcccc4ada2e6c921 is not running
Error response from daemon: Cannot kill container: 9dbd7163ab12: Container 9dbd7163ab123a7904b4251c8de311e176d9b226f50aae1ba4c89ef5a4a23c47 is not running
Error response from daemon: Cannot kill container: c247e109c016: Container c247e109c016b34681d80c15b1438d3c33216f1e29e9d1951630f3991d454a0e is not running
Error response from daemon: Cannot kill container: 3e000acd0ca5: Container 3e000acd0ca584e87f8f03ebfbab10d4702432d7c50e5fdb0c94b7b47179dc30 is not running
Error response from daemon: Cannot kill container: 70d8db2d1cf6: Container 70d8db2d1cf63fdea148791c9a49ae55121f8577da517d7097d1342fd3e31c2e is not running
Error response from daemon: Cannot kill container: 3181ca920dad: Container 3181ca920dad5ff21097d66217fefd8549c1047bc6d2fd580c4007500e23abba is not running
Error response from daemon: Cannot kill container: e7d542f3dd09: Container e7d542f3dd09f393091f073af0347d4dd0191c15f2c723e90fe664bbc7ecc47e is not running
Error response from daemon: Cannot kill container: d9c3a6719f6f: Container d9c3a6719f6ffdef7dc431eae74fdf2964bd474d9a82e491ec2a81766831b0e7 is not running
Error response from daemon: Cannot kill container: cc52d340ca7f: Container cc52d340ca7f81b5837e7972895057a3a20df8e05a2abaebedc240ec122b8399 is not running
Error response from daemon: Cannot kill container: 3de898f0a93a: Container 3de898f0a93a5defc0216743adb18fbc0a0388e38d76b2e936eac7c5fa7bbab5 is not running
Error response from daemon: Cannot kill container: 29b0f1598b7a: Container 29b0f1598b7a458684359b4796baf15c3d4a85d3179d2eeda741f108cc81973d is not running
Error response from daemon: Cannot kill container: 0aaaceadf67e: Container 0aaaceadf67e1be61d11530fb2e7fe250b4fad1015731994e9f0a5b1f92a5d59 is not running
Error response from daemon: Cannot kill container: b5a35a3db335: Container b5a35a3db3355621e8d2a6c2f939d4f51db11057fd2077d14de446264a540b7c is not running
Error response from daemon: Cannot kill container: 03f4c49c2321: Container 03f4c49c2321c7b7103346f56c0e27dc9af1002777d88b01106d98ab3a17824e is not running