GUI acceptance tests using environment deployed from packages.

Build: #2130 was successful

Job: Onezone harvesters privileges add and remove was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
19 minutes
Revision
39fb434fa4268b56f32dccaa52527f3591cd9ea8
Total tests
7
Successful since
#2110 ()

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  47479      0 --:--:-- --:--:-- --:--:-- 47479
Error response from daemon: Cannot kill container: efb493c1e323: Container efb493c1e323a5aef27a728359dec8542612c08e80c452c1d4adc054ecd954a2 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-COHPAR/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHPAR/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHPAR/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHPAR/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHPAR/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHPAR/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-COHPAR/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-COHPAR/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-COHPAR/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 20:27:13.952818     441 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  44740      0 --:--:-- --:--:-- --:--:-- 44740
Error response from daemon: Cannot kill container: a19a75ea56ee: Container a19a75ea56eecfd95bfbe1747e554b156500f63f86eefa2e2e014f35d5ad4749 is not running
Error response from daemon: Cannot kill container: bad5ae8b17d2: Container bad5ae8b17d2e2a6ffbef6eb92fed45aff9f3dc7db30d07295d20dfd899f9d5d is not running
Error response from daemon: Cannot kill container: 77164b999dc1: Container 77164b999dc167179bed3f7ac2ee92585cce58bb65481588d9a7288a399b2b55 is not running
Error response from daemon: Cannot kill container: 5469879eefac: Container 5469879eeface517fc385bc84880dd108a649920889843221a52fcb27f660e1d is not running
Error response from daemon: Cannot kill container: 0c7b66fbd06a: Container 0c7b66fbd06a1078addecca74eeacfca299e93efeb9d2b6abb55637e906102d1 is not running
Error response from daemon: Cannot kill container: b8876a2154ef: Container b8876a2154ef98c505c7d3f953ca5b42cea16ad9ce65cad4eef42fcaabddc32a is not running
Error response from daemon: Cannot kill container: d30450a1ee06: Container d30450a1ee06e93b8650072e52f22992381acc730e51af8435ab23993d793eaf is not running
Error response from daemon: Cannot kill container: 7b5a4631ade3: Container 7b5a4631ade3f552cda9cbf284eb30dfb8a1b65356ab4efdb386dc6a87bff238 is not running
Error response from daemon: Cannot kill container: 61cf24304493: Container 61cf243044936e7732cf35ae76083396d62abb62075e82539ccc054d4291ecfe is not running
Error response from daemon: Cannot kill container: 5b071d40fa79: Container 5b071d40fa79f25a3e960b04b82bc6723ddd9afe46209c48aecc2f13ab7dc34e is not running
Error response from daemon: Cannot kill container: 75e7c9e8aef1: Container 75e7c9e8aef1dbe634b9cdd628f34f25e99916107585d3b79fc96e48c89c3eae is not running
Error response from daemon: Cannot kill container: 56475933e689: Container 56475933e6895fe89009eff63bfec5019e1302187f64a58c93aff0ccc8c318ae is not running
Error response from daemon: Cannot kill container: a65c96407e3b: Container a65c96407e3b5bf52994f6c9d620d9cbde2fb215be290e091d2336bc85bed9d9 is not running
Error response from daemon: Cannot kill container: 1aa424fd81d8: Container 1aa424fd81d8e8f11759ad5bccc16425a4ae96e2dd35856225f32b93f32e2155 is not running
Error response from daemon: Cannot kill container: 63fdd365551b: Container 63fdd365551bb8bf491e0f7112417b3765b3dd5670cc69aca60fad2530893c68 is not running
Error response from daemon: Cannot kill container: 2f0cb5f2260d: Container 2f0cb5f2260d0a41b07f92eadcadf0318ef3fb119096ccaaa08f677402627d8d is not running