GUI acceptance tests using environment deployed from packages.

Build: #1999 failed

Job: Onezone invite tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
44 minutes
Revision
3472d8727468cf978131865efabe3f31a6595f39
Total tests
9
Successful since
#1969 ()

Tests

  • 9 tests in total
  • 1 test was quarantined / skipped
  • 42 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  43896      0 --:--:-- --:--:-- --:--:-- 43896
Error response from daemon: Cannot kill container: ef8491e841ad: Container ef8491e841ada108b7c09b8b81d820c9ce920ec5e86bacc8a415a366d856e4b6 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
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]
W0225 21:29:35.482039     494 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  27210      0 --:--:-- --:--:-- --:--:-- 27210
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: a0f2b6fede6d: Container a0f2b6fede6de7ca60131c778071c010c386939072aedf2d4a77c5fe7b70d6d1 is not running
Error response from daemon: Cannot kill container: 4d32a968db70: Container 4d32a968db709e56c848367f8efc510288957384cdc791f389f54202ff87c945 is not running
Error response from daemon: Cannot kill container: a6d9bcc8046b: Container a6d9bcc8046b5664fb6ab585ffba6b592c16e3699d8797e691c847ee166cbe26 is not running
Error response from daemon: Cannot kill container: 4e38af30f040: Container 4e38af30f040c00849dc2ecb291150d2781ec61848c2821236ab72261d0b4526 is not running
Error response from daemon: Cannot kill container: f8b8744efef9: Container f8b8744efef9b8d7f22984c7ef713bff232d751341c528def808b64dca47c96c is not running
Error response from daemon: Cannot kill container: fd3aceceeda3: Container fd3aceceeda3e9c37c7d8b29bd6359854db3b91c152c21b855ce9822bace418b is not running
Error response from daemon: Cannot kill container: 41502a5471e4: Container 41502a5471e4b9e308e4d0e273901b2eea39406f5dc0cd4ee04971bf21bfb61a is not running
Error response from daemon: Cannot kill container: 3813a2b3502a: Container 3813a2b3502af53f2195be5a90e9677a5c8a4e78b382d4ba44c8776554a1b9f2 is not running
Error response from daemon: Cannot kill container: 9c8eea26030a: Container 9c8eea26030a7aec244f8aa13bf17d4e1cabf81acaca2101d2c5d718d89be733 is not running
Error response from daemon: Cannot kill container: 1e5b085334c4: Container 1e5b085334c47094e1dba8249e28ba8e16231e0c08189816a90ef156ac27b225 is not running
Error response from daemon: Cannot kill container: 5358b58e0732: Container 5358b58e073241f1a0bd0215580cf8a61024526a8187754289ebfb3a15cb07e5 is not running
Error response from daemon: Cannot kill container: eccf148b1dc5: Container eccf148b1dc5bc4fecb765c2a94afdd662f9cb4862a4d96650faca870ade5c57 is not running
Error response from daemon: Cannot kill container: 74041865f5f3: Container 74041865f5f3317b95c3b0b27834df61689096d1b23342f55bf971af6e2b832e is not running
Error response from daemon: Cannot kill container: 39940a245197: Container 39940a2451978d771b91308623e4a1e7a8de94f9e76fdd9e997ff15da50c7dee is not running
Error response from daemon: Cannot kill container: ec9a39b33744: Container ec9a39b33744ece1b658bea6dc55275919a0e3ed9c908c50df5673064a20fa36 is not running
Error response from daemon: Cannot kill container: db5324963cbb: Container db5324963cbbb3e3e658f03ef46c9ad0e7a7478705140c5f0c28cbc69f73767d is not running
Error response from daemon: Cannot kill container: 695639e8777b: Container 695639e8777be7dfe4ff5b4c746b7472861e50889a6af3a17c3e389cf4281cfb is not running
Error response from daemon: Cannot kill container: e06e576749e3: Container e06e576749e3fee278c0cf637e4db1107b8fcaf454af42b7778daceebc0625cb is not running
Error response from daemon: Cannot kill container: efc97ab1e923: Container efc97ab1e92306e6b52021e70d9c7255eebbcaaa6f2f1823aae1d9e167fc286a is not running
Error response from daemon: Cannot kill container: 28d692fa01fb: Container 28d692fa01fb038417f3b905d8d715eea261a478cda4ecabb666a79f9d57da73 is not running