GUI acceptance tests using environment deployed from packages.

Build: #2142 failed

Job: Onezone spaces basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
16 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
Total tests
23
Successful since
#2082 ()

Tests

  • 23 tests in total
  • 15 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  20959      0 --:--:-- --:--:-- --:--:-- 20959
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: 157f67432b33: Container 157f67432b33f549f5c2e1361e2759a78f94244864cb938bf2eb06ca3187c8f8 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-COSBT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSBT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSBT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSBT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSBT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSBT/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-COSBT/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-COSBT/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-COSBT/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
W0518 11:05:19.379994     435 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  46530      0 --:--:-- --:--:-- --:--:-- 46530
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
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: 2bf052220333: Container 2bf052220333a5d45b5629b297f76fd627bdd671455c18c4537448737600ff92 is not running
Error response from daemon: Cannot kill container: bc2af27e4eab: Container bc2af27e4eab3712eea47da323310c77b8121eee6b706725bb7259bf23e122d1 is not running
Error response from daemon: Cannot kill container: 99a2c8861f4b: Container 99a2c8861f4b169053d35e293955efd8cdbe8e4165191f1f25cf0308159a5d6e is not running
Error response from daemon: Cannot kill container: 675464b894c3: Container 675464b894c3e33c3c014ab984c212119d93281ccd450056035bce3961f0cbb3 is not running
Error response from daemon: Cannot kill container: ee78d32daabf: Container ee78d32daabfa1607262a1b088b33c552c13ad3ca00c8bdb4e904b8d5871ffa7 is not running
Error response from daemon: Cannot kill container: 786fe07c430e: Container 786fe07c430e91b88d71f9c2e6b269d15cbebd6c144199ee9816c295fe607030 is not running
Error response from daemon: Cannot kill container: de60f66be22c: Container de60f66be22c275c35202f44efbad6294907af806fe6c46a665e56ee311b5582 is not running
Error response from daemon: Cannot kill container: 2f700cdc10dd: Container 2f700cdc10ddd3362434becbda7ed1d3f272546c088a8096d6f623c0f7179e96 is not running
Error response from daemon: Cannot kill container: 5983a75d581d: Container 5983a75d581d9d05bf063d960d468071cd38c0d9b8594d49bc10eb493c128a76 is not running
Error response from daemon: Cannot kill container: 19c12251203d: Container 19c12251203d676737fd1cdcb55e803e23f61f28aa0cd4818d7ba749c184b979 is not running
Error response from daemon: Cannot kill container: 599a4719b304: Container 599a4719b304777e9e8aa94a4c4ddbb6903c76c1c7366086393a02c40b4b6654 is not running
Error response from daemon: Cannot kill container: 9784603d37c9: Container 9784603d37c9ba3ba0e409393e467a35ecb691e5e709274cf59a56570cdb3523 is not running
Error response from daemon: Cannot kill container: 780fa12da70a: Container 780fa12da70ac7d551ec155673a74e2bc5e4c8189094bc2eb13407077e661146 is not running
Error response from daemon: Cannot kill container: 5133e6757e39: Container 5133e6757e390495d12b2c3574b5d096eb5e8d42f179955b702074e9f024df10 is not running
Error response from daemon: Cannot kill container: c93f4a132354: Container c93f4a132354cfe1cc0f8b20bef11cb9c625a609303ae1de23f74b91fb61b940 is not running
Error response from daemon: Cannot kill container: 7e30c16054c5: Container 7e30c16054c555f459063dd5147bce5e89302c5d94f826555254695d3524cdb0 is not running