GUI acceptance tests using environment deployed from packages.

Build: #2178 failed

Job: Oneprovider ACL subfiles was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
29 minutes
Revision
8046c81cb26d07683c2acee37fe8f6bde9d9a654
Total tests
10
Successful since
#1958 ()

Tests

  • 10 tests in total
  • 27 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  43485      0 --:--:-- --:--:-- --:--:-- 43485
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: 5fc7508579df: Container 5fc7508579df6c3df6e8658acb2fef6db43074f26d2d7f1cf6ef6752a97ffd27 is not running
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
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-COASF/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COASF/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COASF/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COASF/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COASF/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COASF/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-COASF/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-COASF/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-COASF/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error: could not find tiller
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable
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]
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
W0620 10:36:41.268345     446 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  40460      0 --:--:-- --:--:-- --:--:-- 40815
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: 9e015cf0e855: Container 9e015cf0e85533afe29d31f1bb7f05b4efeb7cb48c59ed1b1c03561d5a131a99 is not running
Error response from daemon: Cannot kill container: 4bd7d4b645aa: Container 4bd7d4b645aae0ef0b75af5ac1af871de5b7ab82374b339d478f402cb1d8d279 is not running
Error response from daemon: Cannot kill container: 1737c705843a: Container 1737c705843ada59eff8c5e49616b753936207aa398ded9b1408baf8151b6d7f is not running
Error response from daemon: Cannot kill container: 6c5f6ebb52c9: Container 6c5f6ebb52c9f2d5e705fe71f03ccba53cb15b784211e8091e5604f6a38a4c26 is not running
Error response from daemon: Cannot kill container: 4e579d5c6187: Container 4e579d5c618786a3c0e955b3f039ea864d075458d7e0511180111ddd800ae5a6 is not running
Error response from daemon: Cannot kill container: f296b22f6b62: Container f296b22f6b62302569c770748a6b6c250d355c1ed0bca2a4db62e6bf3f13dd11 is not running
Error response from daemon: Cannot kill container: 7c50ceb53ff3: Container 7c50ceb53ff3927f0253033818f5110d6b615e7568db0601063e0b06d4129334 is not running
Error response from daemon: Cannot kill container: 30967dd2e086: Container 30967dd2e086418d413ac602797b71d4ccc53ee0df6627f867e13fe1654a2c22 is not running
Error response from daemon: Cannot kill container: 9f0c3409ea27: Container 9f0c3409ea2749ef4d37b35cc4481c10de7af01e6a80d9252419419c4b64024d is not running
Error response from daemon: Cannot kill container: 45bae0061ecd: Container 45bae0061ecdcf40a648a4938cb394c6c1e95a019013677f815813df40b2c0ae is not running
Error response from daemon: Cannot kill container: 5d9164271d8e: Container 5d9164271d8eac18716178f5413094ab49cb072985b3e991d4d8fd662f16b1d0 is not running
Error response from daemon: Cannot kill container: 6d53415ddcd0: Container 6d53415ddcd07f155e00cfbfaa0da3d1374b2a7d3cbda4031480a8fa431db9ba is not running
Error response from daemon: Cannot kill container: d12ebf546bc3: Container d12ebf546bc30c0ba0b5e8bf5b7c5b6f0ceb4f177b754c7cdfe2eea53746301e is not running
Error response from daemon: Cannot kill container: ee655a6662f1: Container ee655a6662f168f22914b469035ddf81e41c883d6b07502edcda664b7dfbd542 is not running
Error response from daemon: Cannot kill container: d2b6b58c9854: Container d2b6b58c9854e887b2a612793e0b6c4346d11a028c2a83020d2775907efb57ef is not running
Error response from daemon: Cannot kill container: f1403ebf29b1: Container f1403ebf29b1f68b453b950be5b5bba0d4ecc96e4ef529e8d4b3f75d3ba60fd4 is not running