GUI acceptance tests using environment deployed from packages.

Build: #2028 was successful

Job: Onezone invite tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
25 minutes
Revision
06b7ddbe39e2302126bded895dfde2e9f3fa8004
Total tests
9
Successful since
#1969 ()

Tests

  • 9 tests in total
  • 24 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  36069      0 --:--:-- --:--:-- --:--:-- 36069
Error response from daemon: Cannot kill container: 736638d0c1b7: Container 736638d0c1b7923db8501ecc161547f88d8612a4a7829282710be2019d37f6a1 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
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]
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
W0317 09:55:52.247404     498 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  47000      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: e2744a06f0a8: Container e2744a06f0a8e2460aeb225ca4e6cad9932a1e3bc6cb81e69718177f7dfcd52b is not running
Error response from daemon: Cannot kill container: 2468ad2452f7: Container 2468ad2452f77ad1a74d07689d68e2970989c98829cbaebdc525ee815eb0c7bb is not running
Error response from daemon: Cannot kill container: b16946b42a40: Container b16946b42a40d23e9c71d6707ced8880fc7dae04bbf82c2ed5f411ff9234c344 is not running
Error response from daemon: Cannot kill container: db875644de2a: Container db875644de2a3d474fe3281b70979a5dd8937f6d02547de2cac5cd0f46c0a2d6 is not running
Error response from daemon: Cannot kill container: 61839f4c3fd7: Container 61839f4c3fd7860177767bb5c688155c71c7268f9249d5b6776bcafed101ecb5 is not running
Error response from daemon: Cannot kill container: 38a016aa48de: Container 38a016aa48de99e7323d912fb5cd2984abd484c2ca98c71dd72b3ed9c2f822ba is not running
Error response from daemon: Cannot kill container: ce7dbb815585: Container ce7dbb815585bcf20d8cd538ccd371d6b052e8246a0f77bbb02f12db9f676cc0 is not running
Error response from daemon: Cannot kill container: 6bcb6af5c7ef: Container 6bcb6af5c7ef8cdf45f2ee4b8f4f929081ce6314910a72bf000b67796f0909b0 is not running
Error response from daemon: Cannot kill container: 40f58e8b6abf: Container 40f58e8b6abf8338e1f5865dfcff8e3d6d007fbded3a77e116d1fcafea839dec is not running
Error response from daemon: Cannot kill container: bcd77b5d0ee1: Container bcd77b5d0ee153ae42fa89e15fd8c26cf3990e43c0f9793748bf8da558b00f13 is not running
Error response from daemon: Cannot kill container: a6196b3cd7c8: Container a6196b3cd7c8e0142b3b5b7c7b6ca0cc15bb11563c7601073854d323192ae4bc is not running
Error response from daemon: Cannot kill container: e38ecfb54a45: Container e38ecfb54a4590c3a8e04b706e4748bd9512c23bfb3ee5b0f2c6012bd2bf305a is not running
Error response from daemon: Cannot kill container: e74e3e61b9c8: Container e74e3e61b9c8108d2512f15d5964d8040a4bf1c53c509c8138862f9f49b31db5 is not running
Error response from daemon: Cannot kill container: 61b1d4c18cc2: Container 61b1d4c18cc27a3cd13d7dedf135c32eecd293faba3ba809d54f6e5d49f55733 is not running
Error response from daemon: Cannot kill container: 5e6a5367601c: Container 5e6a5367601c611e7385ee27a4ff6ccacdf768a1c697a5837caab7526cd2645c is not running
Error response from daemon: Cannot kill container: f9bd4f574668: Container f9bd4f574668e5fa3325312305c04157efbbd56210cf5ecdb9782fb82d579200 is not running
Error response from daemon: Cannot kill container: b017bb3d91e0: Container b017bb3d91e0f0d1efa9a01adb646fad9b66f9fcfb68a723859a95289f1b14ed is not running
Error response from daemon: Cannot kill container: 065a888c84f7: Container 065a888c84f74039ee65fa316e40a5027556b6374b70ac3fac02c960945fda6e is not running
Error response from daemon: Cannot kill container: 937beecff0a1: Container 937beecff0a1025d3a36ed05a42916a9a3bb7976a5cbfd87c34675bc45468b48 is not running
Error response from daemon: Cannot kill container: 30bde8c8651f: Container 30bde8c8651f3b1cf17a362e139c00ea785dcc43a659622445f1a452e3f2d68e is not running