GUI acceptance tests using environment deployed from packages.

Build: #2281 failed

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
2 minutes
Revision
8bf7c9f6df4b77754518d5d91f1bda1a458ce27e
Total tests
1
Successful since
#2201 ()

Configuration changes

Job Chrome metadata test with key ODSRV-GAPT-MTC no longer exists.

Tests

  • 1 test in total
  • 1 minute 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  50032      0 --:--:-- --:--:-- --:--:-- 50032
Error response from daemon: Cannot kill container: 37401920f76b: Container 37401920f76bedda4c6aa43d68029ddab9cb748a06859fd6ad77b71a52c3ce2d 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-MTC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/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-MTC/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-MTC/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-MTC/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]
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]
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
W0826 06:44:41.461776     447 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
  % 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  40815      0 --:--:-- --:--:-- --:--:-- 40815
Error response from daemon: Cannot kill container: 88c1dd8e49f9: Container 88c1dd8e49f90af99841375bfe33ceedfa056a5bba0ec40f09f66359cd5b74d8 is not running
Error response from daemon: Cannot kill container: 0e561da9378e: Container 0e561da9378e8800c4517d8c2ad32f340fe1a0fcf5100e09f33e60097f12bfe0 is not running
Error response from daemon: Cannot kill container: cd023772f496: Container cd023772f49688ff5f9bf3f630d8789e95fcf8a098f7fef63c81c54dc82bcd9d is not running
Error response from daemon: Cannot kill container: b1a272dc3c0b: Container b1a272dc3c0b4828ad0633e6415525262cba7e006def643fe154119e6dd0972e is not running
Error response from daemon: Cannot kill container: ce2f12d6c266: Container ce2f12d6c26678205923c0336ad9eef1333f8e28de4c9abc26a67ead945c85f8 is not running
Error response from daemon: Cannot kill container: 6944b5d53443: Container 6944b5d534430bc0c5aafa002dbf1794c833c3edc124644b8d2a3049516662db is not running
Error response from daemon: Cannot kill container: ecee458fee6a: Container ecee458fee6a14c4be494845c88626045a6a78e08820ab01c7ca9b37e242f5ce is not running
Error response from daemon: Cannot kill container: 41d473d96b38: Container 41d473d96b38f0b0e9908cf038be20b4ae74753d2d7221fa7dc01755c8fc44b0 is not running
Error response from daemon: Cannot kill container: 92d72c53235f: Container 92d72c53235faab712e4f4726f8ab445e61993952f6f7cc24ef95e4410168e47 is not running
Error response from daemon: Cannot kill container: a01da2df2cdf: Container a01da2df2cdff225dfcad1e703e26d08d563bec83ef54518a02e176768ecbe39 is not running
Error response from daemon: Cannot kill container: a0a2d8b90245: Container a0a2d8b902455109aba9573cff1d6632d2ee707435dc279ee043812f8cec2d47 is not running
Error response from daemon: Cannot kill container: a85a3399a47d: Container a85a3399a47dcb60393f7afcfd35d0908d8dc93c38e1d77e84d8862d79e52f6c is not running
Error response from daemon: Cannot kill container: 154e1b90669b: Container 154e1b90669b9c293396ebc62055c95876f955f929638632a2074615c86d4ff5 is not running
Error response from daemon: Cannot kill container: 6832868c29e6: Container 6832868c29e685cdb7b20f52c0d4d6f94b8ccb84dd0bdc18023c393ee2685958 is not running
Error response from daemon: Cannot kill container: 42cd0d43b5b7: Container 42cd0d43b5b73acd83fe61e5e7048897c6ca61b445e15716a3f2ee47146d8b37 is not running
Error response from daemon: Cannot kill container: 6125e5c1b566: Container 6125e5c1b5664750f90f4ff88adf40977d0f1efffb7290742df09ee88c01de2c is not running