GUI acceptance tests using environment deployed from packages.

Build: #2008 failed

Job: Onezone automations was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
17 minutes
Revision
0ab5f662c3ea6d31c3ccedd9a5babeeb1a2cc8bc
Total tests
7
Successful since
#1943 ()

Tests

  • 7 tests in total
  • 16 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
Error response from daemon: Cannot kill container: 1f6361ca5bd3: Container 1f6361ca5bd3e84090ac80b34f5f9779e547bf6f58513760ec2fb80673432dd9 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-COAT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/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-COAT/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-COAT/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-COAT/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
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
W0302 21:04:02.384208     453 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  22808      0 --:--:-- --:--:-- --:--:-- 22808
Error response from daemon: Cannot kill container: 389a4cbdfa65: Container 389a4cbdfa6556a1a856b0234e407b984a288e0a165ec10fc425f03f7192933d is not running
Error response from daemon: Cannot kill container: 37b0e6d9d9ec: Container 37b0e6d9d9eca528fdec32d31819d625df3c0b5b15ce710561bea34e073992e9 is not running
Error response from daemon: Cannot kill container: 8bf6aca963ab: Container 8bf6aca963ab374ea45112eb156dbe84e1581593de6ab9cbdae8d0790aaf44eb is not running
Error response from daemon: Cannot kill container: 6b54f2740edd: Container 6b54f2740edd4948ace0c90eae7e86dd0e7c04f4e11c43796aacdc9463fd7093 is not running
Error response from daemon: Cannot kill container: a4b9aad602fb: Container a4b9aad602fb4e62b377aee169da6a237b2f6216028be9da59215154db8aabc7 is not running
Error response from daemon: Cannot kill container: f663a13828f2: Container f663a13828f248e18fb636ac820f5c51990501b932299e838c0380b20262c641 is not running
Error response from daemon: Cannot kill container: 1269be5a433c: Container 1269be5a433c90e8fd338f00e7b3c595c3823258141f51306e169186a8815cac is not running
Error response from daemon: Cannot kill container: 41fd7c1bfe95: Container 41fd7c1bfe952192987c413a8c5996e2b2639fcdbafd823e7250cdb8481f640d is not running
Error response from daemon: Cannot kill container: 322f12075658: Container 322f1207565862168fde49c5f4947801e005d62710b74c52f8115d589bd37a17 is not running
Error response from daemon: Cannot kill container: 934eb7afb8cb: Container 934eb7afb8cb953da3efe9c2223c3dae9c9e19159d3e6d11ed67de267a6df2c2 is not running
Error response from daemon: Cannot kill container: 1285060ad8d3: Container 1285060ad8d3ce5b866d234701e53ef965c275582429889ea25dc34d93b7cce2 is not running
Error response from daemon: Cannot kill container: 5ef59a1b50e5: Container 5ef59a1b50e549ed351b20ecd23549164b4f1436248e9589167a6c248efc67d4 is not running
Error response from daemon: Cannot kill container: b91ef0db0e0f: Container b91ef0db0e0fe38ab9b095d38c0ff5bdbbc35db50a036cdd65a2ebd05deae756 is not running
Error response from daemon: Cannot kill container: e95484799834: Container e9548479983451992324d175b5460d8fcfe38e6f4ffea8c79a063b7616c9bd27 is not running
Error response from daemon: Cannot kill container: 5a78fa9d333c: Container 5a78fa9d333c912b8c0887c0afbc153b584b27983b19086669c041cc174d4b38 is not running
Error response from daemon: Cannot kill container: 27bd35600c71: Container 27bd35600c71e5c11da3d7d00f1595b1d1e4b9e02524cef17292f75b86581eb8 is not running