GUI acceptance tests using environment deployed from packages.

Build: #2118 was successful

Job: Onezone basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
34 minutes
Revision
531283e2b89b3833269b775ff1b3609165404e1a
Total tests
21
Successful since
#2100 ()

Tests

  • 21 tests in total
  • 33 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  41544      0 --:--:-- --:--:-- --:--:-- 41544
Error response from daemon: Cannot kill container: 0454121ebebf: Container 0454121ebebf5085eb0527eaf470f0ab6d0593abe470177735ab3cac9d70c582 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-COBTT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COBTT/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-COBTT/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-COBTT/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-COBTT/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
W0422 13:48:38.476569     440 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  26895      0 --:--:-- --:--:-- --:--:-- 26895
Error response from daemon: Cannot kill container: ca163303b201: Container ca163303b2011debb234a2f1393c6bbce80ac3331dd6db7095181ddd27bca8d3 is not running
Error response from daemon: Cannot kill container: 0125d0f03952: Container 0125d0f03952755a27eb26a907b8ccf04cbd2250d06bfcf891349150ca81d414 is not running
Error response from daemon: Cannot kill container: 51071cea1fa1: Container 51071cea1fa18328acd0195952c7be7ac5332fc47427f0ffb7e6bae434f1b479 is not running
Error response from daemon: Cannot kill container: c285c3cbb73b: Container c285c3cbb73bfee10632f0ec660a7a6fb73f24c4d52e63e117254d0a2d7ab3ee is not running
Error response from daemon: Cannot kill container: 930e86c3bb77: Container 930e86c3bb77aa7af918f944077a5c1d4076c77ca7c9ebd14dc24959a48e8751 is not running
Error response from daemon: Cannot kill container: bb4065dfce6b: Container bb4065dfce6b19e7b903bb0eb6379ab8caac46f50306f2d1f05974feaf14ff12 is not running
Error response from daemon: Cannot kill container: d5f15b0b33f5: Container d5f15b0b33f56947117a59d9a81dc7b1975884345d5c15e2f7fe2a8f04e20fdf is not running
Error response from daemon: Cannot kill container: 431f71cc4d44: Container 431f71cc4d449ea30b74910ad5e5e412039cd0dbd76d11c290ff4b8c0a18cac1 is not running
Error response from daemon: Cannot kill container: 4d844cdc895e: Container 4d844cdc895ec6aa007170f8b60d0217e50e32a3e299ef49694e6fd5d74d6338 is not running
Error response from daemon: Cannot kill container: b2918fbce3ff: Container b2918fbce3ff63128bcdc709dcffb10bbd2c912d00eb4cffea9fbb41706210a6 is not running
Error response from daemon: Cannot kill container: fe9d26ee3150: Container fe9d26ee315052538fd1ea739e512d34f171e6cfe6d73342c45a5f2307271434 is not running
Error response from daemon: Cannot kill container: f3574f52c179: Container f3574f52c17962606268fc70bfe2fba2433441ae6eb1625148304a923e450fc4 is not running
Error response from daemon: Cannot kill container: 196c8504b9b9: Container 196c8504b9b9472c4ccad5f3930fd1fcc82ba5b85f2d17227a449768928d5419 is not running
Error response from daemon: Cannot kill container: eba9e3cf7843: Container eba9e3cf78432814a7949b8cc016e3d09f4290c90ce1a914fee95bd3983abc55 is not running
Error response from daemon: Cannot kill container: 8fb1e433846e: Container 8fb1e433846e416be22b2bdd590b03eee35f8aeb8333d99e8861a2c8e817c2f7 is not running
Error response from daemon: Cannot kill container: 5aca1e75bedf: Container 5aca1e75bedfecc5834350b8f237e051c268a35f675aebaab1213d302d1e353e is not running