GUI acceptance tests using environment deployed from packages.

Build: #2015 failed

Job: Storage sync charts was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
6 minutes
Revision
ad27c13068a0a0493e4f5d695cb720cbab343e5c
Total tests
1
Successful since
#1976 ()

Tests

  • 1 test in total
  • 6 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  46530      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: cbe5a2c5c776: Container cbe5a2c5c7766f370192341b1dc189cb45641cab123273733b52952e7ca23460 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-CSSC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/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-CSSC/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-CSSC/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-CSSC/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
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
W0304 20:59:12.913516     467 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  41918      0 --:--:-- --:--:-- --:--:-- 42300
Error response from daemon: Cannot kill container: 9c92f5aea451: Container 9c92f5aea451d5c8f7b2b48197c68e4212fb584cd4bf78e80c0e43143cfeb21e is not running
Error response from daemon: Cannot kill container: 6adb64954800: Container 6adb649548004cb7cfc88de602129588c324c5f67b839670f0135f5b77369808 is not running
Error response from daemon: Cannot kill container: 770e47025c04: Container 770e47025c04ee028749ba8e8e400633ce548533acb2c2ea937fbba070900f5e is not running
Error response from daemon: Cannot kill container: be230edb9ef2: Container be230edb9ef2e6fc8fd71e4d4194e6dda25328444c64d3c969abce876abdf51f is not running
Error response from daemon: Cannot kill container: 8071d69f56ae: Container 8071d69f56ae5abfc6a7d17b7d5782014a3f28778af02996ed33b515ce9e197f is not running
Error response from daemon: Cannot kill container: 783e0f8d1b14: Container 783e0f8d1b14c4797377bc36dcdcd671351b5e360a3030a549f35a74b2dc008e is not running
Error response from daemon: Cannot kill container: f4cf8e356308: Container f4cf8e356308572b0864a324145d9d33e465787cde2df75a751a13235b3772e8 is not running
Error response from daemon: Cannot kill container: f0e755eaffa3: Container f0e755eaffa3d718f53db0ba8754c0154d46a7156ae7a1310b80a64e7a66d187 is not running
Error response from daemon: Cannot kill container: 088d4a828547: Container 088d4a8285479ab195c7fd96498fe0e1b298f8e5b058b79d5eda33c4a033753e is not running
Error response from daemon: Cannot kill container: 5d813d2855d5: Container 5d813d2855d51f9a43e5ec387fc7df13dc7477cd7ca9b1855c2ba86358d6f308 is not running
Error response from daemon: Cannot kill container: ecaf30dd726e: Container ecaf30dd726ee69106431f8659986e957fbe6988aaad2af9389ad727e17656b4 is not running
Error response from daemon: Cannot kill container: 5267bbb03202: Container 5267bbb0320283cc9a223d833cb65bc4830fee42fef261892a83ca66a622cc57 is not running
Error response from daemon: Cannot kill container: 1e980b1078c3: Container 1e980b1078c32388011c9c013a096e62a432ab9feaa2ba44fde61ab16572a346 is not running
Error response from daemon: Cannot kill container: 2bbe246c34e9: Container 2bbe246c34e9c9c1d1144655542bde76d5b0872f159b5b2158e68902f6efd91a is not running
Error response from daemon: Cannot kill container: 0daa3d25bfe5: Container 0daa3d25bfe5cdfb38e9543a35e50f30567dde5def478171e31fef38a29e6133 is not running
Error response from daemon: Cannot kill container: 9ec555c33007: Container 9ec555c33007bf17f3e58e9cd8166ddf0c0645ef4f468dfac3af8d9f4990ad4f is not running