GUI acceptance tests using environment deployed from packages.

Build: #2142 failed

Job: Oneprovider ACL subjects was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
12 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
Total tests
7
Successful since
#2007 ()

Tests

  • 7 tests in total
  • 11 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  48468      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: 53483eae2d62: Container 53483eae2d6298af786715d3fa3f3834fc3ec71695c75c3eda9b765a5ee96757 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-COABS/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COABS/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COABS/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COABS/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COABS/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COABS/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-COABS/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-COABS/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-COABS/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
W0518 10:52:39.592730     444 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  33235      0 --:--:-- --:--:-- --:--:-- 33474
Error response from daemon: Cannot kill container: e90cb5cb8171: Container e90cb5cb8171b8c585a09b1a153ffbb19d0779b6a18b444071bf4adb1004c0d7 is not running
Error response from daemon: Cannot kill container: 8577eecc9a3f: Container 8577eecc9a3fe448843d0e515d5a206cd4b8ac56573a2ee582ad63a61bdbf1a9 is not running
Error response from daemon: Cannot kill container: 302ad24890b9: Container 302ad24890b9af900f833b66de5e81d974620e269fb24643906a7bfeeada8ddd is not running
Error response from daemon: Cannot kill container: cdb12848e507: Container cdb12848e507912efa39e3dd7d7375bebc5030035e50f0506d57ccc00333381d is not running
Error response from daemon: Cannot kill container: 148953fc8947: Container 148953fc894778224ec12176ea1d8f51765eec653a631c94e19bc97d58c2614d is not running
Error response from daemon: Cannot kill container: a514489dd26d: Container a514489dd26d5ba234860744a6a1435e0e711d9559b824920597f96b28bd4be0 is not running
Error response from daemon: Cannot kill container: ced771aad09c: Container ced771aad09c73a59e53bc6d80d6290df28c9f95b02405f72958fcac44bfaae0 is not running
Error response from daemon: Cannot kill container: f92c699b6ced: Container f92c699b6ced1405fc1dc23628b58f88b03d37cc4155a7c828b6cb2e1e01b0c6 is not running
Error response from daemon: Cannot kill container: 9e73fb4445c0: Container 9e73fb4445c04a69a4c6e138e72f64a206f3d890ec5d01250cd72513a79ed5c1 is not running
Error response from daemon: Cannot kill container: e1340b8597ee: Container e1340b8597eefa1a8dbf0e344ce695ecbefc18266432be5f764241745b92b3f5 is not running
Error response from daemon: Cannot kill container: 3368351db1bb: Container 3368351db1bb3fe641668fef5af78e3f87c928fc318244503375d57df862e15f is not running
Error response from daemon: Cannot kill container: d86ef01be581: Container d86ef01be58168422dfd83593e695b937c7ae8e316a1300ba646c504d8e122e0 is not running
Error response from daemon: Cannot kill container: a6606887c87e: Container a6606887c87e30c654ae3716f679132c6ad74f7cd39647c2147413eb76c6ccf0 is not running
Error response from daemon: Cannot kill container: 97813b2b1431: Container 97813b2b1431b107b2ef65f309dc94d36c455a590e15b3be699a1a4d02df1ab7 is not running
Error response from daemon: Cannot kill container: 6d1e9a2514f8: Container 6d1e9a2514f8bdb986b6a1faa0b904ab957bd84c1e6616787dc5c2abe01826d8 is not running
Error response from daemon: Cannot kill container: 039d6498a7b4: Container 039d6498a7b4435e47ebc8954ed58ccc8f75bdf48cc2652cfa91640dec92d111 is not running