GUI acceptance tests using environment deployed from packages.

Build: #2163 was successful

Job: Onezone automations was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
21 minutes
Revision
2a6ac951983b0da397726653daa1ebcdbbe74ca8
Total tests
8
Successful since
#2152 ()

Tests

  • 8 tests in total
  • 21 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  47969      0 --:--:-- --:--:-- --:--:-- 47969
Error response from daemon: Cannot kill container: 4ce84d23bc01: Container 4ce84d23bc01db6a884f6a489536b01f9e2f6bdf09a4fdbda276513f8435ca5a 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-COAT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/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-COAT/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-COAT/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-COAT/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]
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
W0603 19:56:04.563601     441 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  38775      0 --:--:-- --:--:-- --:--:-- 38775
Error response from daemon: Cannot kill container: 9fd9773f0bf5: Container 9fd9773f0bf5c7066aaa3fbd935c6b67ebb80ab659a7a03ca5d108dd138d2a10 is not running
Error response from daemon: Cannot kill container: 7eb057222c0f: Container 7eb057222c0fc69edfa69e2400b831463ec10fd0f2f21dab985b8f5f505ed5f2 is not running
Error response from daemon: Cannot kill container: 7781230974f2: Container 7781230974f276d3a04a291a0d905093861283db86019c489ea9da459caecaca is not running
Error response from daemon: Cannot kill container: e5cecff58395: Container e5cecff58395253523529b1b94ab159e203332016c77cb715f5eb68ada720827 is not running
Error response from daemon: Cannot kill container: 72d3ec7bc160: Container 72d3ec7bc1607f765cd1fc3733425f7dc6d0741cb8d7631b77e9d08a8f5afaff is not running
Error response from daemon: Cannot kill container: 7cd2ce67c5d1: Container 7cd2ce67c5d162b549956f13b1e636b4e11aa526a976747f22d9e35a32e20ef8 is not running
Error response from daemon: Cannot kill container: 6426264daf4d: Container 6426264daf4d52483675d94175168c450ef08c6bb926114b3674ca0df10f6a3b is not running
Error response from daemon: Cannot kill container: b1fa05ee5ff3: Container b1fa05ee5ff31c5ef2236f8d811905547cf3c7088fb7a00771814b0f8d4cf245 is not running
Error response from daemon: Cannot kill container: 8bb2c97feebd: Container 8bb2c97feebdfa43ae6d10403cc4d835483ca45aa91c4e7277042b015761a0d9 is not running
Error response from daemon: Cannot kill container: a33a8d8b644c: Container a33a8d8b644c22213704224879734189311e80f26a8be68cf4d57006cc095c22 is not running
Error response from daemon: Cannot kill container: 718dd0ee01f1: Container 718dd0ee01f191386a42bb0158915b3d79d5c8e024c6a9e6feed011702561fd2 is not running
Error response from daemon: Cannot kill container: 08d1b785367a: Container 08d1b785367ac732fd8a8cb8df2005040002f21920a4d48a463cdfcdc65396c3 is not running
Error response from daemon: Cannot kill container: d1c2acaade80: Container d1c2acaade80d73abe3477eb42ac68227ccd4e4b1521203a2d1fdf04ba5260e6 is not running
Error response from daemon: Cannot kill container: 91b7b0c17447: Container 91b7b0c1744720e23a7748e43ccbba5c6544d54790484fa092933999f09dbaf4 is not running
Error response from daemon: Cannot kill container: 5db2b56923a8: Container 5db2b56923a853aa3923d61e008a2b096d388f9fa555d72d0e4caf602c40b697 is not running
Error response from daemon: Cannot kill container: 1033c7e678c9: Container 1033c7e678c97121f0a4790b65607ce177889954638a1820d723f7523c781958 is not running