GUI acceptance tests using environment deployed from packages.

Build: #2129 failed

Job: Onezone spaces multiuser was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
17 minutes
Revision
39fb434fa4268b56f32dccaa52527f3591cd9ea8
Total tests
13
Successful since
#2113 ()

Tests

  • 13 tests in total
  • 17 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  50032      0 --:--:-- --:--:-- --:--:-- 49500
Error response from daemon: Cannot kill container: e394d82cb404: Container e394d82cb4045c9dea3e0fb87ae7ec8a731bf769d108f9a57c2422988eefe612 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-COSMT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/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-COSMT/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-COSMT/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-COSMT/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
W0504 11:15:29.155147     443 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  26895      0 --:--:-- --:--:-- --:--:-- 26741
Error response from daemon: Cannot kill container: 537b07bb3b4b: Container 537b07bb3b4b405ef51df3c83280a46f860b4b12d0a1a3ed8b4a0260da9f10ba is not running
Error response from daemon: Cannot kill container: 4f0c6efd27ad: Container 4f0c6efd27adaec5509f1ff4676208786206e97cc971be69043aafc679c1c411 is not running
Error response from daemon: Cannot kill container: bd2279c48521: Container bd2279c48521485c374908e52e108a3d03252401592e72c905ac473335a2df06 is not running
Error response from daemon: Cannot kill container: 222c8dc2725c: Container 222c8dc2725c1ce86039f0ec144bbf26c9b715afc0a43c2ee35a36bf34c8d639 is not running
Error response from daemon: Cannot kill container: 6e701d1845a2: Container 6e701d1845a2d24cefbf6bbbf6a6287c3eecae15de122a8c9244e0d0c854dd2b is not running
Error response from daemon: Cannot kill container: 57403d7b4313: Container 57403d7b43139d18777ec319a1eba36b3c0a5ecd3a9b6143cab55e81930738f7 is not running
Error response from daemon: Cannot kill container: 3947c35fe5d1: Container 3947c35fe5d1fa0d8ad04812dd7790cc4571419dbebec74082a5904ff5426505 is not running
Error response from daemon: Cannot kill container: 319d26637678: Container 319d26637678d67764aad2aea617f46270a3c3d23a615eff0a27f55c68d6bdd3 is not running
Error response from daemon: Cannot kill container: 3fd4a440e171: Container 3fd4a440e1714a90841052ade4d216acaf98d3f1f6f2be51b1a1af4a98e029ac is not running
Error response from daemon: Cannot kill container: 23bae3608a90: Container 23bae3608a905082656db4a10f1d73a0d4b8111e987cf526d8c2f1fd61e9fdba is not running
Error response from daemon: Cannot kill container: 867db40a9759: Container 867db40a97595e7cf95333624067cf59b7ef80489b333a70643475d7157543fd is not running
Error response from daemon: Cannot kill container: 91ca53eecb41: Container 91ca53eecb416862538c929f4762074fcb14cddc3386a2a980b7e4559054648c is not running
Error response from daemon: Cannot kill container: 492891b10a15: Container 492891b10a15aa90ed8d3f014b6000a453767d4d276fe481f67e42248cb9aa84 is not running
Error response from daemon: Cannot kill container: 9d51abe8690b: Container 9d51abe8690bc37556ecee10f5f7e8f318407e1cc5e808929368d1152b4139be is not running
Error response from daemon: Cannot kill container: 35eb891874b5: Container 35eb891874b5403ba4182fdc7cc78ee212e10f63cf674ac2219733c97f2f0f03 is not running
Error response from daemon: Cannot kill container: f42fc3040571: Container f42fc30405711f0c9f4beca364df055017da9c3c472591f2d969d509e94fb79c is not running