GUI acceptance tests using environment deployed from packages.

Build: #2006 failed

Job: Transfers directories was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
20 minutes
Revision
0ab5f662c3ea6d31c3ccedd9a5babeeb1a2cc8bc
Total tests
5
Successful since
#1990 ()

Tests

  • 5 tests in total
  • 19 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  42688      0 --:--:-- --:--:-- --:--:-- 42688
Error response from daemon: Cannot kill container: 44d3acebe9b9: Container 44d3acebe9b9e22eb88b0a2c1534b76cf1dcabe165c9108a475409f31690ad7a 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-CTD/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/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-CTD/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-CTD/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-CTD/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
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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  18034      0 --:--:-- --:--:-- --:--:-- 17965
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 9d265ddd448e: Container 9d265ddd448e05de58a72e1c867d02259ceafe669ed5007faedbac7a754351cc is not running
Error response from daemon: Cannot kill container: 74082864b5bd: Container 74082864b5bd2c3395a217ff454229270f7abf95e8e5372aa98317903e32fca4 is not running
Error response from daemon: Cannot kill container: c70d799a209d: Container c70d799a209d8b4582780e46ce5248f4bf16a4157e04c5b792d62eeb05e661e7 is not running
Error response from daemon: Cannot kill container: c1e11ce13f6b: Container c1e11ce13f6b0c93270caf8331f3ab36c5e31b4b5329d166ce8272416c92834a is not running
Error response from daemon: Cannot kill container: 41b09ac2fdc7: Container 41b09ac2fdc7d778950e6ff4a9a0a87f0b1c3bdb2dd644b1b17b8c700acd9aa0 is not running
Error response from daemon: Cannot kill container: b69bf3253778: Container b69bf325377859f8525a3e769e9b0f03de15b14cc4320bced7f53e7a8b80c5af is not running
Error response from daemon: Cannot kill container: db6ff5e3cdbd: Container db6ff5e3cdbdef6aea893290a955689b247e3e7a8a186b8c71f4595884c33514 is not running
Error response from daemon: Cannot kill container: ab1109f81f06: Container ab1109f81f065cea493afaec9874c04571ca2eb475d01fcc219ed8bf3183b9a0 is not running
Error response from daemon: Cannot kill container: bae173a643e9: Container bae173a643e9b676869f6e28af9d5e78c0f25c5b08b575d41586b5dec996264a is not running
Error response from daemon: Cannot kill container: 9a647d681259: Container 9a647d681259d7803f97253b20e1aea3720c96b1aa220ba43c71a456cd022ca5 is not running
Error response from daemon: Cannot kill container: 5be04feb6837: Container 5be04feb68376821dd7a08a6cf5f23ceb3c75ae79472db98133129cb03cbf238 is not running
Error response from daemon: Cannot kill container: 095f5af7e833: Container 095f5af7e833240e512fa84332ef02fb9fbb2f8bed732bc9f42610704248e816 is not running
Error response from daemon: Cannot kill container: 95380aa490b1: Container 95380aa490b1745adc060e6bb8d06c9209ed3f99741aaef6f03272c3f1ec5cf2 is not running
Error response from daemon: Cannot kill container: d7ae1f1cd01b: Container d7ae1f1cd01b8a0341d3b0364c50710708734cc874e449125e0b70effbc5801c is not running
Error response from daemon: Cannot kill container: c5d24cb795b7: Container c5d24cb795b723c43cde12a976340a2011ae1cceb0dd3ed395253d4a6743a3af is not running
Error response from daemon: Cannot kill container: 46d6785f74cc: Container 46d6785f74cc0c18aec7de684dca92379aeae380d19664c80d8c524e9e755cd5 is not running
Error response from daemon: Cannot kill container: ce85e42be7bc: Container ce85e42be7bc00ee458954625e8674aa86bce89192defacb40f9bde413ce6b27 is not running
Error response from daemon: Cannot kill container: 00a44aa518ea: Container 00a44aa518ea2d2b65a767f238d229e6b59c43ceb7e7c99dde3e5ac3f5938550 is not running
Error response from daemon: Cannot kill container: d0fb36d9a66a: Container d0fb36d9a66a0a6b9892e3a0a8b328b0ca25392127c2593c502d166fa5c5c8ba is not running