GUI acceptance tests using environment deployed from packages.

Build: #2130 was successful

Job: Onezone harvesters index metadata was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
21 minutes
Revision
39fb434fa4268b56f32dccaa52527f3591cd9ea8
Total tests
7
Successful since
#2129 ()

Tests

  • 7 tests in total
  • 1 test was quarantined / skipped
  • 20 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  38775      0 --:--:-- --:--:-- --:--:-- 38775
Error response from daemon: Cannot kill container: d0a798ac061a: Container d0a798ac061a0fd9894dcc14a244816312ce48664e1b2d9910c1b568f0abe0da 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
W0504 20:25:23.000161     439 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  41176      0 --:--:-- --:--:-- --:--:-- 41544
Error response from daemon: Cannot kill container: 34e76bf9327b: Container 34e76bf9327bb5c807f4501fa96bf99220b8f79c05d9a7e8c6189d993fe1a5c2 is not running
Error response from daemon: Cannot kill container: fb718de6d87e: Container fb718de6d87e8de553261349dc5278ed95be12b05962501e680e506cdb72eb16 is not running
Error response from daemon: Cannot kill container: 5d10519b6906: Container 5d10519b6906093ac8dd20be74bcb8a70e3446aa102ef2bcbd3e59451d0e4692 is not running
Error response from daemon: Cannot kill container: 752b11f2eee8: Container 752b11f2eee81cda7c07dc5756731bcb1b94a3b04f688902752c9c0a21c6ff41 is not running
Error response from daemon: Cannot kill container: 2e65783046e5: Container 2e65783046e5e56b2e4c9caec6e20ad86c010e56eaf24b6675df4fc309b7bb4e is not running
Error response from daemon: Cannot kill container: 099fd7dcf0fc: Container 099fd7dcf0fc7409cde2d2dc5990f9525b56c56bcefde9f07cc824c1c0a0fc01 is not running
Error response from daemon: Cannot kill container: 8e5c16dda92d: Container 8e5c16dda92ded7bd8b35463a67448f989dae012e58574de9f709fbf1a6599bb is not running
Error response from daemon: Cannot kill container: 62561a2e8bd3: Container 62561a2e8bd3a4fa505ce5ef4b6ebe778304588c1052490f55a73608561b18c8 is not running
Error response from daemon: Cannot kill container: 23df13219ad0: Container 23df13219ad0a2eb3796496a6ca05a2a32435441ce57ce61866163143b6e535c is not running
Error response from daemon: Cannot kill container: e7ba156b5358: Container e7ba156b5358cbaf676177949b9bc8ae39bfcaa6b5404590ab00686b28fffbea is not running
Error response from daemon: Cannot kill container: 699c75bf76db: Container 699c75bf76dbc52b9ff2cf89f7f8ed2de963982aa01e407ba94c7473218a4dc1 is not running
Error response from daemon: Cannot kill container: e07f92f3d3e4: Container e07f92f3d3e41be58605ac0bc3f41fbc72668bb8393946a3cd60842dcd963aab is not running
Error response from daemon: Cannot kill container: a4b9355240a7: Container a4b9355240a74b5fc60a17b3ddb88d23215447bee62204437952ca4b0b32f943 is not running
Error response from daemon: Cannot kill container: 86af085f08c1: Container 86af085f08c1b2ab11a7a50b85e8b3486fa447a56c261762bd9b5cb66d2acf1a is not running
Error response from daemon: Cannot kill container: 55c0920e74ae: Container 55c0920e74aec68193a8eaf188413c4e6a70e5496d8563ca6d86f3c6f2e831cd is not running
Error response from daemon: Cannot kill container: 650a8f91f6cb: Container 650a8f91f6cb738f8c1e660fa4b365b27a7bfd642e294599c30b5aa844e8c5d2 is not running