GUI acceptance tests using environment deployed from packages.

Build: #2058 failed

Job: Onezone tokens delete was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
21 minutes
Revision
f9849bc17b2b7fe665e2a7df5ed9e5dea86d8360
Total tests
10
Successful since
#1965 ()

Tests

  • 10 tests in total
  • 20 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  43896      0 --:--:-- --:--:-- --:--:-- 43896
Error response from daemon: Cannot kill container: a00bc8832dd0: Container a00bc8832dd0cbeb6c07199008e327cb34ee68434dba885df1da23dc178abaf8 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-COTD/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/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-COTD/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-COTD/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-COTD/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
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
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]
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
W0325 23:25:40.247087     500 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  26588      0 --:--:-- --:--:-- --:--:-- 26437
Error response from daemon: Cannot kill container: b3380086f094: Container b3380086f094afbd1a0b357098a2b410f449a0e8b39b44c4580c6dbbbc0ce43f is not running
Error response from daemon: Cannot kill container: 8d0b366f4535: Container 8d0b366f45354551b17471389710589db89d11dba0fc8da118f3147baa53ed32 is not running
Error response from daemon: Cannot kill container: e991ab3f97e2: Container e991ab3f97e2fe5781b6bc90daed4fc8960850ba6dc88926c64803c06006c699 is not running
Error response from daemon: Cannot kill container: 79871125d5c2: Container 79871125d5c2624c1342a35dec21ed22c7a7d855c4b33fbf0b8329a1442ee07b is not running
Error response from daemon: Cannot kill container: 5ab2c7eea9ac: Container 5ab2c7eea9ac8295cbb63e42124f5a43d211c93f3b6817cee49c4b95ca8d6804 is not running
Error response from daemon: Cannot kill container: 3354fc107c5a: Container 3354fc107c5a26b00ac86424d9c3651de93acb1788132781aebfe61ca10bd02a is not running
Error response from daemon: Cannot kill container: 5cc14078e0f6: Container 5cc14078e0f6dd66f4537a102880165954367c3ec5a23bc1a292980a5f8b843f is not running
Error response from daemon: Cannot kill container: cfb9713573d6: Container cfb9713573d671bdefda9ddcf991e55886e71791e63f72f8d4a97a3ecbe706da is not running
Error response from daemon: Cannot kill container: 5d567fdc451e: Container 5d567fdc451ede56c418bfb86eebab127723695a68edfc2e3a2b7cb78c97d9b1 is not running
Error response from daemon: Cannot kill container: 6036b866e2a3: Container 6036b866e2a32d4e87ba2273711361326cd2223cfc5c189313ea5ae15b595278 is not running
Error response from daemon: Cannot kill container: 002ffafc93b0: Container 002ffafc93b086bcb083e4314b6951e0f5dfc31444a8dda0445de03fd4cb642d is not running
Error response from daemon: Cannot kill container: 43e58f92d3d7: Container 43e58f92d3d7e086413c4fb2bd449a10c2f8ea92e0481172c361f22a787ed1e1 is not running
Error response from daemon: Cannot kill container: fbe5a84f0d47: Container fbe5a84f0d472ac9d1a51d9093edb8c635f6eb51903c1a068eec6207d2cba534 is not running
Error response from daemon: Cannot kill container: ce853ba3d2a9: Container ce853ba3d2a9bba4b2cdf6df682c514f7fb76a8d0a4e57f08a0e900fa3c3f92c is not running
Error response from daemon: Cannot kill container: 01927f2eb886: Container 01927f2eb886d89f3acc731ee90d817336ebae81cd46e10e05005c94592db9ff is not running
Error response from daemon: Cannot kill container: e926fda79b38: Container e926fda79b38438a6fb66606b7356b785aa9c56fb103eb0639b98d84965604be is not running
Error response from daemon: Cannot kill container: 88b03cda63f3: Container 88b03cda63f3fa02ca8e4086041d5436cb82c0e1baf6a4960cb49088dd318a86 is not running
Error response from daemon: Cannot kill container: db409a2100a2: Container db409a2100a2404d86e9c681f398dd1f9ed0d5ee990b99dd5975a427810d8c84 is not running
Error response from daemon: Cannot kill container: 46a62a7d68fd: Container 46a62a7d68fdd491d81f3650de884295b7c6c54c3ee6595f2c30953a118a9d9d is not running
Error response from daemon: Cannot kill container: cfb519c2a1ab: Container cfb519c2a1ab715cfbce386172b3e00c2c5c0c2b390e49880155cf8c13ad6a9b is not running