GUI acceptance tests using environment deployed from packages.

Build: #2272 was successful

Job: Onezone harvesters index was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
2 minutes
Revision
624ddd1dfa241fb01c10e610d5a920a26351648e
Total tests
1
Successful since
#2201 ()

Tests

  • 1 test in total
  • 1 minute 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  40112      0 --:--:-- --:--:-- --:--:-- 40112
Error response from daemon: Cannot kill container: bbd95f938c86: Container bbd95f938c865332e72c70a8e1d8539669d8a220f7e5f7f98e8c860a0768bebb 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-COHI/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/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-COHI/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-COHI/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-COHI/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
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
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
W0824 16:14:12.750373     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  45617      0 --:--:-- --:--:-- --:--:-- 46069
Error response from daemon: Cannot kill container: dfb1ff5b6e0b: Container dfb1ff5b6e0b636954c5ee2f9539ecccabdee048edee9a0a35753193c53c3a0f is not running
Error response from daemon: Cannot kill container: 2b823544d016: Container 2b823544d016dccad6fab883f288732068ce34a806368f8d8013c299b9f8c883 is not running
Error response from daemon: Cannot kill container: 90ddb600c8be: Container 90ddb600c8bebf5f1d8f7a989e618ff50a86eccdccfa62f6ba2c14d1d969b13d is not running
Error response from daemon: Cannot kill container: 4d3fbb71170b: Container 4d3fbb71170b1d3a084ac54091744e98c1d800168e8730d572638c70054ee591 is not running
Error response from daemon: Cannot kill container: 73415ae6c077: Container 73415ae6c077db07e991dc4f13705557a936640b504d0e8793f532f42f6fc96d is not running
Error response from daemon: Cannot kill container: c6d5c770efed: Container c6d5c770efeddbdcf071e4e303ee41db2c51366e2a3da3f383a0a4d6d8c0fd6a is not running
Error response from daemon: Cannot kill container: 5cfb745cc05b: Container 5cfb745cc05b8d18c839b65f16a5bce793f90c4f6bb1b522640c1cc9d6be6950 is not running
Error response from daemon: Cannot kill container: 21f51c6960ae: Container 21f51c6960ae87a62df106254d628308e02c6167dc0252bd7116aeb95507f0f9 is not running
Error response from daemon: Cannot kill container: a0b872af1653: Container a0b872af165341b1d2dca07849a46094027c73f0324c9ea09cee375e7c332c76 is not running
Error response from daemon: Cannot kill container: a389e1479098: Container a389e1479098b5f2cb37b579b26509bd452426b423ba9ddbc27820579993826e is not running
Error response from daemon: Cannot kill container: 4cfffe670921: Container 4cfffe670921824eaaf8ede22290968841dfff2b1a931d94e04ac38428b3f26a is not running
Error response from daemon: Cannot kill container: b4beba22ac56: Container b4beba22ac56957503f1d7a79a739a8836683a08e60c577a1199cdc12754b390 is not running
Error response from daemon: Cannot kill container: 3f4890f9b10b: Container 3f4890f9b10bcc9352c06357fb243aa7d35c2044872db0135afac7ceba01eead is not running
Error response from daemon: Cannot kill container: 6b23359a6d74: Container 6b23359a6d74a3896abec5f3e05ba80a37f6923e54bfc8381512c6d3352a42d9 is not running
Error response from daemon: Cannot kill container: a473c82d38a5: Container a473c82d38a5992f03e9e7f728daecd9b9f6da30d1a783cfe22e0dd4a1d668cf is not running
Error response from daemon: Cannot kill container: 65d60feeaf42: Container 65d60feeaf42be94ceeac2058f384e3a55819f58911a8821e9e924f25d8adffa is not running