GUI acceptance tests using environment deployed from packages.

Build: #2127 failed

Job: Onezone providers basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
10 minutes
Revision
531283e2b89b3833269b775ff1b3609165404e1a
Total tests
8
Successful since
#2082 ()

Tests

  • 8 tests in total
  • 9 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  49500      0 --:--:-- --:--:-- --:--:-- 49500
Error response from daemon: Cannot kill container: 510ca765703f: Container 510ca765703f57bd958e0377639c258ecc564570c7a0378918400be160dbeba7 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-COPBT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/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-COPBT/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-COPBT/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-COPBT/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
W0429 22:12:07.914711     505 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  18105      0 --:--:-- --:--:-- --:--:-- 18105
Error response from daemon: Cannot kill container: 6127c81b85d4: Container 6127c81b85d4763b798cb91703d63d0f7c78d508cefdf868c337d49d08d37e54 is not running
Error response from daemon: Cannot kill container: 09c62bbb0098: Container 09c62bbb0098263d492ffddb26e8d78d27ff7524c67d3f63c5f412af2fd4206a is not running
Error response from daemon: Cannot kill container: a88875e86e0f: Container a88875e86e0fa35255ddfde1640610dd9955df8928d62ba802a15af0c42ed47b is not running
Error response from daemon: Cannot kill container: 9fa9ab3ee348: Container 9fa9ab3ee348d09f0e77083d37d6902015e9d41e5ba643bec061676ed262e1b3 is not running
Error response from daemon: Cannot kill container: 271fc4400dc2: Container 271fc4400dc23dfe22f388a442b950a0b99d23725c93b470ddc1d4e6108d70d6 is not running
Error response from daemon: Cannot kill container: 736f03254b4f: Container 736f03254b4f4ad5902afa24f84c84d03ea470f32ff620e4bc0db8ed45390e7a is not running
Error response from daemon: Cannot kill container: 1551520de24f: Container 1551520de24f1f085212a8e5006b4bd694cd6f2124755f2c45a38203b5d37f19 is not running
Error response from daemon: Cannot kill container: f020dead3f5a: Container f020dead3f5a253fe0927108be6c13fee9a3db7653aba4094e29ae1941980ffc is not running
Error response from daemon: Cannot kill container: 809c1d848652: Container 809c1d848652536b4879b02ed48992f3ceda817bd83e7619157f51e5cbe64832 is not running
Error response from daemon: Cannot kill container: 628542724ca3: Container 628542724ca3a6fee64b90a81480d9048ff686d8a68056b30653faa5ec5f5929 is not running
Error response from daemon: Cannot kill container: 87ecafb820c5: Container 87ecafb820c5843e93ae57748b3357c3a31b7138522eacdf3441aef15d9aa5cc is not running
Error response from daemon: Cannot kill container: fb2b735b35a4: Container fb2b735b35a47ecec0af1bd127374c0b07d5a9e1609f893e29de3e041d21dc77 is not running
Error response from daemon: Cannot kill container: 504156d6179b: Container 504156d6179be7ba24ab830f57df4a7b880847e4fd091fa223e132a9a643e2e2 is not running
Error response from daemon: Cannot kill container: 722c3bbb9f17: Container 722c3bbb9f17ed432e8c57bd30a5ee3846bd32b5a264fc5232d8526172070295 is not running
Error response from daemon: Cannot kill container: 0d4be3c10cc0: Container 0d4be3c10cc00d0f7a02798e8097f5e159071c0a92ec8fb138ed3ff54ee618cc is not running
Error response from daemon: Cannot kill container: 425c22e9875f: Container 425c22e9875f926a4a31ea47f54caac57c29d52ca0c2e42490ccc552b4f06ca9 is not running