GUI acceptance tests using environment deployed from packages.

Build: #2192 failed

Job: Storage sync charts was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
10 minutes
Revision
466b4a1341ba42e3ce27e138642da6627c86d0c6
Total tests
1
Successful since
#2191 ()

Tests

  • 1 test in total
  • 9 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  39100      0 --:--:-- --:--:-- --:--:-- 39100
Error response from daemon: Cannot kill container: 72621aba886d: Container 72621aba886d6978a604bf85d1b11433c7e29c70a83b939e8bad396b93ed85b8 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
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]
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
W0630 22:41:53.349233     454 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  27696      0 --:--:-- --:--:-- --:--:-- 27696
Error response from daemon: Cannot kill container: d986bc61a051: Container d986bc61a051e8b736e6776b971458ce64680a8fd48e18bdec673ff9c519fe34 is not running
Error response from daemon: Cannot kill container: c7f2207363e0: Container c7f2207363e04b97f7d701371dfee84b380d39c2591f46eef438609c84ad4c1b is not running
Error response from daemon: Cannot kill container: 5cc9dad7a72d: Container 5cc9dad7a72d9276b3e37284b4c4e1806e747a0a765c2d9145482fe158f78bab is not running
Error response from daemon: Cannot kill container: 266035f32603: Container 266035f326034cc43378f39abf75e018cda2032c496b1276099483e37bf33ebf is not running
Error response from daemon: Cannot kill container: 67051d70e68b: Container 67051d70e68b8dd2b35bc61b9bbddb14d99d06b474c0f2bbe0801a4cf3a23a46 is not running
Error response from daemon: Cannot kill container: 4ffd955d9801: Container 4ffd955d9801e0847d993d57b496e659aadea907df3ac1a3610af1b4b16eb002 is not running
Error response from daemon: Cannot kill container: 173d8ffebb5a: Container 173d8ffebb5a72fb66893a5f6104f8511c403bcc1e2e7c65940607565d8ca70e is not running
Error response from daemon: Cannot kill container: 0d7692ff3ad5: Container 0d7692ff3ad5165545b7509ac46c7dffc767416b5a81e0c00c79843199167693 is not running
Error response from daemon: Cannot kill container: 00fcd3906395: Container 00fcd3906395d2b5d5c13f1a07a7eb73557e3a72bbac7823561d80efb45664e3 is not running
Error response from daemon: Cannot kill container: 8f2ec88656ae: Container 8f2ec88656aeb116d8c5d1c8615cc715de50463edd90173b343c35abc8054133 is not running
Error response from daemon: Cannot kill container: a0bbee1bab6e: Container a0bbee1bab6eee4845dc13e6d9e3826f4fbf5c82cc643b3c7a0f6ae2d197e714 is not running
Error response from daemon: Cannot kill container: f5fc707325a3: Container f5fc707325a318772ed14574406ee05e982b6f5680a5f86b466abe24723ac4b4 is not running
Error response from daemon: Cannot kill container: 4ae37c6c98c8: Container 4ae37c6c98c80570f831dc3012aefc258530138ec5be1c57ad2a5db56b2dbf98 is not running
Error response from daemon: Cannot kill container: 85d2cdc56935: Container 85d2cdc56935ad314762e7d6ae24506d6e44b39254bfbc7b6cc9308779093230 is not running
Error response from daemon: Cannot kill container: 05804a8cd821: Container 05804a8cd821c2583ff22e332d2b0964c656c547687e0f7ad4235769ed8d282d is not running
Error response from daemon: Cannot kill container: b97e7722701c: Container b97e7722701ce7f6dad427dd82ca8dbfcd943adfc4fa16de19085dd32b14aad4 is not running