GUI acceptance tests using environment deployed from packages.

Build: #2140 failed

Job: Shares basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
16 minutes
Revision
dfd405a02fa2a4bab1ba6431bc2638a43a9cd1cb
Total tests
18
Successful since
#2112 ()

Tests

  • 18 tests in total
  • 1 test was quarantined / skipped
  • 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  47969      0 --:--:-- --:--:-- --:--:-- 47969
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: b7b4776e4d6e: Container b7b4776e4d6e386023c2d7b4e77ef817013066a01a3688ef138606094eb28a9d 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-CSBT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSBT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSBT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSBT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSBT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSBT/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-CSBT/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-CSBT/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-CSBT/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
W0516 19:56:20.342956     437 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  17692      0 --:--:-- --:--:-- --:--:-- 17692
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: bda900f360cf: Container bda900f360cfbd8cbdb55294e9dfb536234ccb8b3316db27b8f8d19f822bb006 is not running
Error response from daemon: Cannot kill container: 735e446cf741: Container 735e446cf741b2fb340a62df6f9ceb5c6f69a5ef4c38336d62b7c6a98033dee4 is not running
Error response from daemon: Cannot kill container: 3b971a869f5e: Container 3b971a869f5eda5cafa304ee7403b675083a5346036e38e8fb5a6fda15780cce is not running
Error response from daemon: Cannot kill container: 82fdaa5f2506: Container 82fdaa5f250611cf138d25995f0888f286b508743fe5476373b48e30078b9e2c is not running
Error response from daemon: Cannot kill container: 3164440d4e05: Container 3164440d4e0579ba711d76a947e3a04479914b001e82156b2f97393138ddc211 is not running
Error response from daemon: Cannot kill container: 59e6f47d8bd8: Container 59e6f47d8bd89fb46f5d28e4df186614eba770dde7e422dde00994c9f09bb9ea is not running
Error response from daemon: Cannot kill container: 7d5227850212: Container 7d5227850212815331baab4e260e6d1a790b85c89d3fc09ffc773ec87b85cab3 is not running
Error response from daemon: Cannot kill container: 14ac300283d4: Container 14ac300283d463e5b968bcc29488d4c6f457bce618b82d91880f6ad9d7164c29 is not running
Error response from daemon: Cannot kill container: bcb6a42151c3: Container bcb6a42151c3a5e4b3c261715908fee859ea8068c599bc88e3be5dd364e76946 is not running
Error response from daemon: Cannot kill container: 6a740668e213: Container 6a740668e213adfc8f54757b6e24cadfa39eba00fd711093a00fb3c5178b01e5 is not running
Error response from daemon: Cannot kill container: 827c8c2fb8b9: Container 827c8c2fb8b96df7d995058a868c99140f1b7ee16b311912130d8766212ab762 is not running
Error response from daemon: Cannot kill container: 68a1e5178c74: Container 68a1e5178c74953deaf0067421e183c355a88cd2698a598bb50c3d7d7b17e3fc is not running
Error response from daemon: Cannot kill container: 54f043db17a3: Container 54f043db17a350308b69aa6e64d4831b568d27fa94508c65bdd0b95bb38e5970 is not running
Error response from daemon: Cannot kill container: 1bb22a8da743: Container 1bb22a8da74377fcaa6ab00e7e48fa152c2611c5f577c778d9cf00d952228cae is not running
Error response from daemon: Cannot kill container: 4a742da02558: Container 4a742da02558e001441c3f2302b57dd802f37ba7659a206317f7ece182ef9815 is not running
Error response from daemon: Cannot kill container: 5f4567dffb55: Container 5f4567dffb55762db7f190c6d263d72f06a1a7e32a66cc9a2ebe1e7d74b23c0e is not running