GUI acceptance tests using environment deployed from packages.

Build: #2133 was successful

Job: Onezone harvesters index metadata was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
29 minutes
Revision
8490c925f492c6fa084fa157e3410fcfda0ec6eb
Total tests
7
Successful since
#2129 ()

Tests

  • 7 tests in total
  • 1 test was quarantined / skipped
  • 27 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  18686      0 --:--:-- --:--:-- --:--:-- 18686
Error response from daemon: Cannot kill container: 237cb2d14a47: Container 237cb2d14a479a40433e1e640349bb5b128eb0b098cd13dcde2135a5d144e580 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
W0506 08:18:07.480991     435 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  38454      0 --:--:-- --:--:-- --:--:-- 38454
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 431172fa1bf0: Container 431172fa1bf05cb591a324647f7f5c8a28bdb96e3bee07fdeb76b805e09e7927 is not running
Error response from daemon: Cannot kill container: e3ee66852f33: Container e3ee66852f33c305d164ad53e6a1ff5324271aca34cc78822ab774ca7d913e53 is not running
Error response from daemon: Cannot kill container: e2a11bd9337b: Container e2a11bd9337bb75d72b30d3990d6b6e2a41344361f3aad5f0aa7f16cc457829f is not running
Error response from daemon: Cannot kill container: 4ab682db0080: Container 4ab682db008060bfce5e55e8a2e33ce6c4ecb6ecae49c3d680dbf999b06a1b49 is not running
Error response from daemon: Cannot kill container: 3f215b4572c1: Container 3f215b4572c1759de44d52e8e8cb90c6f7b0c7e5be1dbb93c9be1042c2c4ac84 is not running
Error response from daemon: Cannot kill container: e14aed9efc19: Container e14aed9efc19a6ed70b43e1c725b5716d40a2fb72755919b3c202cb4e14aa8d5 is not running
Error response from daemon: Cannot kill container: 00d46f6a359d: Container 00d46f6a359d67cbb5a1fcec0f66f6826a2cc569fb5612a53f8c5d30b60b42bb is not running
Error response from daemon: Cannot kill container: 3755b9d18ea9: Container 3755b9d18ea9bd1d75739baa238c9a27b531409f437e7736a958991c0ede4da3 is not running
Error response from daemon: Cannot kill container: b09dcb86c888: Container b09dcb86c888b1141cf90fccdceccfe003014cbd55e431d3685b8db7f8cca31d is not running
Error response from daemon: Cannot kill container: ac9196983970: Container ac9196983970af3a680768193643db52edcd8fb8f69e3c13e6ae6612c0ac26aa is not running
Error response from daemon: Cannot kill container: df148ff143f7: Container df148ff143f7e744419e9bf1ffacc06fde61d502410cbaf84a974585dbe2e8e6 is not running
Error response from daemon: Cannot kill container: d773400572e0: Container d773400572e064d313b98497e63b7fe64a5982aae87fe7c79526eaf0aefab542 is not running
Error response from daemon: Cannot kill container: 1605a6cbba26: Container 1605a6cbba267daca46597b8e48154865f0cb78db748eb68781bc3ea03851454 is not running
Error response from daemon: Cannot kill container: bf11dffd7295: Container bf11dffd729560f307683a534fca7633253bd5da21d141d48d092c62c4696ead is not running
Error response from daemon: Cannot kill container: 5ef3d4873198: Container 5ef3d48731980851ffd65ad9bc38c21d51f7f86a564d111e603c56cedd9c391c is not running
Error response from daemon: Cannot kill container: cd327c95a6dd: Container cd327c95a6ddf9b6ee59fd99b8cda801b6d149033d2f8918beb6e640b4ed84b5 is not running