GUI acceptance tests using environment deployed from packages.

Build: #2183 failed

Job: Chrome onezone automations tests was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
54 minutes
Revision
3e03531a9135db305f145c67e729e44a9ecef612
Total tests
37
Successful since
#1998 ()

Configuration changes

Job Chrome onezone automations tests with key ODSRV-GAPT-COZATT no longer exists.

Tests

  • 37 tests in total
  • 53 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  44740      0 --:--:-- --:--:-- --:--:-- 44740
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: 84bf36441c4f: Container 84bf36441c4f2c2b789f874c12ce3105a66d20481e8a017955d8b8bc96960814 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-COZATT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/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-COZATT/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-COZATT/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-COZATT/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
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
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
W0627 20:11:04.076395     458 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  18612      0 --:--:-- --:--:-- --:--:-- 18612
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: f3bf2030a197: Container f3bf2030a19700cdf14440c0cc939755abf796b0ea6e03781400571c8e0529a1 is not running
Error response from daemon: Cannot kill container: 8e4fb8f5c88a: Container 8e4fb8f5c88a8565e90a782a07f33cba30925008f5eea8cca4d2ace59431bc58 is not running
Error response from daemon: Cannot kill container: 8d75c203c580: Container 8d75c203c580a23e445253aafb3c9d8b675f21dffd4b8c1085d7e117a06659b2 is not running
Error response from daemon: Cannot kill container: bc11466b994b: Container bc11466b994b93d791555f2e33cae5fb5f4730fef4113a5ce6dc11ca6c90242e is not running
Error response from daemon: Cannot kill container: de2874939f69: Container de2874939f69606df5dba243902b4491d793b6a6fd57813cf4305581307798e4 is not running
Error response from daemon: Cannot kill container: b3667f570f66: Container b3667f570f66909f876edf0f82c8940cc31e3e46f737c9e1f2900c85e58b48b4 is not running
Error response from daemon: Cannot kill container: f7f8120b434a: Container f7f8120b434a76fbb9fbd4727f5eb012bd14b075b7e1f2306de278f6eb4d520b is not running
Error response from daemon: Cannot kill container: bbc732cc24b8: Container bbc732cc24b8a572898664016223cf71ae217e10a0479971be8b1322cbe637bf is not running
Error response from daemon: Cannot kill container: 744de3f1680d: Container 744de3f1680d0f2254c1a8cbd6ae10984dcddd7d2eda99f4d1c4e9d9d2313c03 is not running
Error response from daemon: Cannot kill container: c086cb3db59b: Container c086cb3db59ba8c556a22813c668c1b81da0d19439c2cc02b2353596879b972d is not running
Error response from daemon: Cannot kill container: a6afe574c53c: Container a6afe574c53cead66d36b8b6f7896acb6531d307b2c0dc5787a085c87c40ef00 is not running
Error response from daemon: Cannot kill container: fb2b4560b9d1: Container fb2b4560b9d167869b9a6bd984e84fb6a6bff3bff9e11c3ec97e732671020814 is not running
Error response from daemon: Cannot kill container: 953bcdf60eef: Container 953bcdf60eefd808c6db41ad89ab4bb4c5af149242215ee1ef0b5888cfc0bdc3 is not running
Error response from daemon: Cannot kill container: 580936dbaad1: Container 580936dbaad1eee495955525d0e4eee83e5a7fadee02decb544926504af30827 is not running
Error response from daemon: Cannot kill container: 07972be029c8: Container 07972be029c8eaebf447312baead2159945d28536c683ba14aafbff93c71e775 is not running
Error response from daemon: Cannot kill container: 5a66d2db74b9: Container 5a66d2db74b9d88e9dc6961005794bef84856b7218028b78eaa031e0df98c3e0 is not running