GUI acceptance tests using environment deployed from packages.

Build: #2165 was successful

Job: Oneprovider symlinks was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
36 minutes
Revision
2a6ac951983b0da397726653daa1ebcdbbe74ca8
Total tests
17
Successful since
#2129 ()

Tests

  • 17 tests in total
  • 3 tests were quarantined / skipped
  • 34 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  44314      0 --:--:-- --:--:-- --:--:-- 44314
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: ab971677efc3: Container ab971677efc3c21469faed5fd5cc4084a10faf2f69135053b96da6d5991990cc 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-COSL/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSL/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-COSL/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-COSL/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-COSL/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]
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
W0607 21:27:10.705303     452 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  39769      0 --:--:-- --:--:-- --:--:-- 39769
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: a2a0f54c2cc8: Container a2a0f54c2cc8dce0ebb5f107a95c27ccda37ec5da1dcdf554782a14ace119e7b is not running
Error response from daemon: Cannot kill container: c4c5587a87b3: Container c4c5587a87b36c0e21c6ae94d97794e32ed14612effb83048610d26bc983fa62 is not running
Error response from daemon: Cannot kill container: acfdd1c5fb22: Container acfdd1c5fb22ef430257a439abfcedf600377372175a902cb39eb94f38dc105a is not running
Error response from daemon: Cannot kill container: 3597e99b5aa4: Container 3597e99b5aa4ad62b69759ec9815f628e49e6c4bf0c1b5b96944e522a07261fd is not running
Error response from daemon: Cannot kill container: 676fb7aa91b3: Container 676fb7aa91b386f961d5836474a5f2aebb999c2215b3fd791ebf862f27dc47d6 is not running
Error response from daemon: Cannot kill container: 13f5c8d3a9c3: Container 13f5c8d3a9c36ac454125ab55bae271d67e9db56d18189393d093e7660dbc5c1 is not running
Error response from daemon: Cannot kill container: 41090a43a2b7: Container 41090a43a2b709d6f65131dc69afbb0acd6f7089283fd7abfeb2cd55638d1c4b is not running
Error response from daemon: Cannot kill container: 47fd6b6fb83e: Container 47fd6b6fb83ef1619b7fd2c3c3d9676a55e09c182f7236a47459df3ee3e8e776 is not running
Error response from daemon: Cannot kill container: 0bdb1893da7e: Container 0bdb1893da7edafb58c4d75ecbb138bcf7d3de3f3ac9f859dcb8c458275c4c29 is not running
Error response from daemon: Cannot kill container: 3effecdc474c: Container 3effecdc474cc2cfaa9807b3a6bb9681ac69c5802bff157186c41a2e673ad452 is not running
Error response from daemon: Cannot kill container: 5ec8884aabb9: Container 5ec8884aabb913abdaf1bf9a612147d8aca0aab94cdfb8efba0222181aba24ee is not running
Error response from daemon: Cannot kill container: b47e33568246: Container b47e335682463092ed14107fb7953b2aa3d30edd21402c73b78871c2d1d49250 is not running
Error response from daemon: Cannot kill container: 78f1885514f2: Container 78f1885514f2412ba811b1f9f1c925ffe1e04702caea6e488864a57a237c7b7b is not running
Error response from daemon: Cannot kill container: 127d80513e6b: Container 127d80513e6b52967ff925f599d5493a2fb9024a1b6c5ad3b80747164a2ffc6c is not running
Error response from daemon: Cannot kill container: 18b35901bcfd: Container 18b35901bcfd8b8158926ac09b4db446fc7449a3a1ff5790e32fd6101d6f4601 is not running
Error response from daemon: Cannot kill container: 8c90c78694be: Container 8c90c78694bef69aefb7a8a7af14fd403701e39d98964ff97d7fcbce6669eb80 is not running