GUI acceptance tests using environment deployed from packages.

Build: #2006 failed

Job: Onezone harvesters index metadata was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
19 minutes
Revision
0ab5f662c3ea6d31c3ccedd9a5babeeb1a2cc8bc
Total tests
7
Successful since
#1997 ()

Tests

  • 7 tests in total
  • 18 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  42300      0 --:--:-- --:--:-- --:--:-- 42300
Error response from daemon: Cannot kill container: e551d13cfcec: Container e551d13cfcec3c4e372752a6f15aa71fdd0fb3c88a4564dea4f9d7ab7943ea07 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-COHIM/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHIM/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHIM/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHIM/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHIM/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHIM/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-COHIM/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-COHIM/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-COHIM/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
W0301 11:49:18.189478     438 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  42688      0 --:--:-- --:--:-- --:--:-- 42688
Error response from daemon: Cannot kill container: f9a823a83d52: Container f9a823a83d5257a043f5ee3716afef3d7926f91eb7d130f96ec8fbee29d1432b is not running
Error response from daemon: Cannot kill container: 1d1f870d1870: Container 1d1f870d18709ec3e5adee1718d93c0e9d632c9eea3a011448cec10670b8e7c5 is not running
Error response from daemon: Cannot kill container: c1a82852cb53: Container c1a82852cb53bedb96d89920b7905d92b59a690a112ee91c2f280d1b6ea5a160 is not running
Error response from daemon: Cannot kill container: 244f034bb514: Container 244f034bb514d873a56782730c277e90bca8a8bad91c4f7d0b623c8a8fa5eb88 is not running
Error response from daemon: Cannot kill container: 7f9aa3e4cca1: Container 7f9aa3e4cca1aa26eacb0566513f52032689a2be6b5930f216f01a309485e194 is not running
Error response from daemon: Cannot kill container: 141d06b19397: Container 141d06b19397167872239c1bfac000346458a9981676cf45dd1e5e3e48537f2f is not running
Error response from daemon: Cannot kill container: 7ffb1b1a3bc4: Container 7ffb1b1a3bc45362755d6d42a18a07d6430516141226ed35452f2d7f63fa5e41 is not running
Error response from daemon: Cannot kill container: fffc1a112c94: Container fffc1a112c949fde5498285868005dc5d8a70b8368868d5ff7cb94ba90b32d3c is not running
Error response from daemon: Cannot kill container: 52b4f8fd5231: Container 52b4f8fd52319eff0db75d72765aa26ee122eae51915d3eed87784206376bf71 is not running
Error response from daemon: Cannot kill container: 5a3a0455cc3c: Container 5a3a0455cc3c17126e90ed883b9e8be50a297d235abce7edf3a991483648b358 is not running
Error response from daemon: Cannot kill container: 86254dbd071b: Container 86254dbd071b51ad39114e6ac240fccb5c577369ae23da474169d4a6ed2de0a0 is not running
Error response from daemon: Cannot kill container: d704ef7e1065: Container d704ef7e1065c2084e711e704fa8bacc0195bdfe121903527d2d32b3713f1209 is not running
Error response from daemon: Cannot kill container: e7c4a9be4e73: Container e7c4a9be4e738f77a9a71409d7b38d1f28433fb88e872fbd506990c7e21baad3 is not running
Error response from daemon: Cannot kill container: b0b0c009af62: Container b0b0c009af6217cc3da2bccdf3421aca987c1ab680eb78a40036f68000eb80c6 is not running
Error response from daemon: Cannot kill container: 04b2b016b3e5: Container 04b2b016b3e53922cc63594d26900a7f1b9f0b59146f641820a937b260ac4726 is not running
Error response from daemon: Cannot kill container: 5fcd20f322ca: Container 5fcd20f322ca725513c56f720da865fdca7ab7b9aa330e9b75cd153e2bc5bbe7 is not running