GUI acceptance tests using environment deployed from packages.

Build: #2142 failed

Job: Oneprovider ACL subfiles was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
29 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
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  45174      0 --:--:-- --:--:-- --:--:-- 45174
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: c1ef4e9ebf14: Container c1ef4e9ebf14e3cd05fa116210dd4987fdfe0a6318511a22a0c58860dea44170 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]
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:11:05.844074     442 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  32089      0 --:--:-- --:--:-- --:--:-- 32089
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: b582adc42317: Container b582adc423176a0875084395fe876dbb3d225a7584e675651e7459477b85856a is not running
Error response from daemon: Cannot kill container: fba0a5ae35f7: Container fba0a5ae35f74729f9b8db816cf74ed4820bab4873ec77c7b21567df422a1d81 is not running
Error response from daemon: Cannot kill container: a3f3f4e5476b: Container a3f3f4e5476b0124000dea92ee8893b3382f509079f895440503a7ded76a1868 is not running
Error response from daemon: Cannot kill container: f187c32d58c5: Container f187c32d58c5447a9345cd50f98cbdebc6c57632efa33a3cbe8493307b3ced4a is not running
Error response from daemon: Cannot kill container: 50893e0992df: Container 50893e0992df1b6cbf1f8e95fef4b2212c68503645db2a3a90ec017e9a0aa475 is not running
Error response from daemon: Cannot kill container: bc8f59091ccb: Container bc8f59091ccb66b2516ac3a8b31ce46e0344ebe5493263aab12a6a059a2c60b5 is not running
Error response from daemon: Cannot kill container: bc2b8719cc0b: Container bc2b8719cc0b938cfb866869abb56fb54f5655bf53a52fd4fb4572194de6f90b is not running
Error response from daemon: Cannot kill container: 341dfa7d14e3: Container 341dfa7d14e3a061481252e950900e431fff6bd9d4c18e7ed2f1f6638ef170d2 is not running
Error response from daemon: Cannot kill container: 5a4b19e29679: Container 5a4b19e296792123cccd07d01c9a44bd4b14e5ff24fa6e4f1d76e6eafcfb22fe is not running
Error response from daemon: Cannot kill container: 5df4e2090c73: Container 5df4e2090c735b35c2bce4504b9f6cd7b2f534b0bf0f6c1f531e7e73d65eddf1 is not running
Error response from daemon: Cannot kill container: 365635ce9c66: Container 365635ce9c66f320ccbf079a17df200183a712b93f062a321508c28e255653ec is not running
Error response from daemon: Cannot kill container: 43588aa6b81b: Container 43588aa6b81b7a32bdf6634baf9aacd2d455c6a0c3a151fa1418bae5b038653b is not running
Error response from daemon: Cannot kill container: a5c40811bed2: Container a5c40811bed2416a095d86662f40b3697386efb39b57d04c40026ca4d605b43d is not running
Error response from daemon: Cannot kill container: 4ec266efa4f1: Container 4ec266efa4f1973d6b5e4b355066cf971f5fc96058806512b79e636c56efd0ca is not running
Error response from daemon: Cannot kill container: a1aa9f97dbc8: Container a1aa9f97dbc8b72e0f848d68b111914115bb7e9628b1eb6c4884d00143c05eb0 is not running
Error response from daemon: Cannot kill container: ba640990de51: Container ba640990de51d9f41e41f33f909f515d305a6ef4c44f2d84ec37dc1cdbbab251 is not running