GUI acceptance tests using environment deployed from packages.

Build: #2253 was successful

Job: Onezone providers basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
18 minutes
Revision
a286f0f6f3f012eb6568be58a9820a7399524818
Total tests
8
Successful since
#2149 ()

Tests

  • 8 tests in total
  • 1 test was quarantined / skipped
  • 17 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  37829      0 --:--:-- --:--:-- --:--:-- 37829
Error response from daemon: Cannot kill container: 652fc9ec4902: Container 652fc9ec490212e5ef7dcc158335773729898bde4e2a7cec1cfbc4b33f7a6b87 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-COPBT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/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-COPBT/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-COPBT/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-COPBT/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
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
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
W0803 20:46:51.293133     507 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  38775      0 --:--:-- --:--:-- --:--:-- 38454
Error response from daemon: Cannot kill container: 0200df6110e8: Container 0200df6110e828f4c78a73bd7e71c8d8f5cb35fe0b4c5d5c4ea61b4a5a7ad2cb is not running
Error response from daemon: Cannot kill container: 83eaddeb3805: Container 83eaddeb38053290914aa9af5eed6ef803f42d7f8f8055163e85ea0045d13b1a is not running
Error response from daemon: Cannot kill container: 1b4fb11af42c: Container 1b4fb11af42c552aa89cd58790b302d6de9405235b90277c2bd3ec54f3dbd68f is not running
Error response from daemon: Cannot kill container: faee82f0a5f5: Container faee82f0a5f5b2b1224f9c643c57588f7d5669ab869567ed73f8052281ad8788 is not running
Error response from daemon: Cannot kill container: ee71d015e9c9: Container ee71d015e9c9da0b72663d8a2a55f9e3de6c4e872c6c3ad47d363da3ecb0648e is not running
Error response from daemon: Cannot kill container: bf49b83c4bae: Container bf49b83c4bae5b729d77aefaa1b25ba92a170fea5b7ecd2f82929860e8a95312 is not running
Error response from daemon: Cannot kill container: dfe7e0949421: Container dfe7e0949421edc43fa1371370df8f4e8c2f457b0fee558d51df4f503dc470fa is not running
Error response from daemon: Cannot kill container: 6c5e9dc6af27: Container 6c5e9dc6af27984cd1f785d034c2c206689a2d40bfa64abaa127c0c9a2979240 is not running
Error response from daemon: Cannot kill container: 1a4db8cff97c: Container 1a4db8cff97ca7712fabb5bacafffd6935b6f978092d4f952426e59714bb4b76 is not running
Error response from daemon: Cannot kill container: e30a76ed4f67: Container e30a76ed4f67150a1c218562eb7360dde8f83b7c6bd6d34db58a692e59e68fd7 is not running
Error response from daemon: Cannot kill container: e3e3a642336a: Container e3e3a642336a46c59a79e0ffe9b18e9edab56a1d8178e32fb366c685fefa1816 is not running
Error response from daemon: Cannot kill container: 9a67e42dd255: Container 9a67e42dd2554c9a326ae40036d0bdc492285abd9b2a60deeff38f8a75a1b52a is not running
Error response from daemon: Cannot kill container: 3adbb9680cff: Container 3adbb9680cff7cd2fe2c27c2fdbcf798e92c7f2e4440de6865615b8862e1eee7 is not running
Error response from daemon: Cannot kill container: aacd28b5b6fe: Container aacd28b5b6fe37f3fe27210831553eb6d94c3db746f46091bc1ff6ebb62c8c7c is not running
Error response from daemon: Cannot kill container: 6eb831993a90: Container 6eb831993a90c3377c130a7faaadc824be13c24e7e5ff86be6ef283ed4df397d is not running
Error response from daemon: Cannot kill container: 3cd2b83c4700: Container 3cd2b83c470076de6f44aee85ad60ef72196d7dc936c8bd7c87c284292070394 is not running