GUI acceptance tests using environment deployed from packages.

Build: #2134 failed

Job: Onezone basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
22 minutes
Revision
72d4158537fcbe5e765cfeaf323ebd441ede24a2
Total tests
21
Successful since
#2100 ()

Tests

  • 21 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  41918      0 --:--:-- --:--:-- --:--:-- 41918
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable: Name or service not known
Error response from daemon: Cannot kill container: a67419e63715: Container a67419e63715c90d010e85bcc96c6c4286603a6be1f890dd4aac578ff99351ba is not running
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-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-COBTT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/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-COBTT/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-COBTT/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-COBTT/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-os-03-s3-proxy-dont-disable
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-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]
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
W0506 12:34:23.889013     436 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  43083      0 --:--:-- --:--:-- --:--:-- 43083
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable: Name or service not known
Error response from daemon: Cannot kill container: eddf91478697: Container eddf914786978398ba72a28c872cb72a0deb693c73acb441d9d44461bef5c7eb is not running
Error response from daemon: Cannot kill container: faabbcf09b92: Container faabbcf09b9298f5dee5b9018b0b71ea661f7de3bddd209ce4c575fb1510bd6b is not running
Error response from daemon: Cannot kill container: 3899b599d482: Container 3899b599d4827c31897ca474f168eb20d6bda413f1d922d86b14f5d51b603a47 is not running
Error response from daemon: Cannot kill container: d4a970f25bd5: Container d4a970f25bd55e6886d0669b7638aa74f760e38ee8f095dc79f3399c5c9c6a1f is not running
Error response from daemon: Cannot kill container: d3215a48343f: Container d3215a48343fef0762974add7bb64201a787a77a537f9640dcd19cd1c4c08476 is not running
Error response from daemon: Cannot kill container: 712afe0a9fb4: Container 712afe0a9fb4ce17d7b01ad533828fb52c48296dd0a5d958a01359627916b25c is not running
Error response from daemon: Cannot kill container: 682dc52d1824: Container 682dc52d1824158032225fe84b79ebd7ae8ffa8cbee88c54c5a31d234676aac2 is not running
Error response from daemon: Cannot kill container: 0c32b9d4cad2: Container 0c32b9d4cad29542cd03ac5fac10a6bc8356b007c378d39154229afe2ebc8f23 is not running
Error response from daemon: Cannot kill container: 8bbb46fc2481: Container 8bbb46fc24817ecfe6af2f2c2b287824e41870caff1a1b8881fbcc57310597e4 is not running
Error response from daemon: Cannot kill container: 664cd12a2875: Container 664cd12a287564d950991b5f60478a92273a2c9eb7c6fa053227a71b44b24d1a is not running
Error response from daemon: Cannot kill container: 6879cf21a4e7: Container 6879cf21a4e7dbe4c950c222e318834fdd2a644c9d8b37c8f1c89b448e87f72a is not running
Error response from daemon: Cannot kill container: c92e0310cfd1: Container c92e0310cfd15e5118273505d04ba1bc188c2443878c3529ee3c195908924e57 is not running
Error response from daemon: Cannot kill container: aa8f33d04500: Container aa8f33d0450061e62fdff9449df01efa4aa35ad4b58c4b96b6e8156632bd1a95 is not running
Error response from daemon: Cannot kill container: 6f5831b708cc: Container 6f5831b708cca0523a073cbcf60777d67a086a9f4e93dab8b213d003508c76ff is not running
Error response from daemon: Cannot kill container: a1f2191bce55: Container a1f2191bce55e6e912d51d40a8bee6d1255c6fe4b4dabef0c0a9d9227476f623 is not running
Error response from daemon: Cannot kill container: 2aa706d91bfe: Container 2aa706d91bfe9568e1e580b225fca3fa74303b2eff231e90b80a863e1b538dfe is not running