GUI acceptance tests using environment deployed from packages.

Build: #2140 failed

Job: Onezone harvesters index metadata was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
20 minutes
Revision
dfd405a02fa2a4bab1ba6431bc2638a43a9cd1cb
Total tests
7
Successful since
#2129 ()

Tests

  • 7 tests in total
  • 1 test was quarantined / skipped
  • 19 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  48978      0 --:--:-- --:--:-- --:--:-- 48978
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable: Name or service not known
Error response from daemon: Cannot kill container: dd4279339c22: Container dd4279339c22615fbda1ea4f12a99b812b83abdc067157eeee5eea2d8468ff8a is not running
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable: Name or service not known
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
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable
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
W0516 20:16:27.202018     442 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  46530      0 --:--:-- --:--:-- --:--:-- 46530
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable: Name or service not known
Error response from daemon: Cannot kill container: df204a3e2af2: Container df204a3e2af23835f359b99b5bac0f3e1e57193e01ca46e099d6885535fe283e is not running
Error response from daemon: Cannot kill container: b795edc02a19: Container b795edc02a191e96c2e673609ac251aa178358c6c1160a5818b86bea1e2bbb17 is not running
Error response from daemon: Cannot kill container: 967634d19ccc: Container 967634d19ccc5ab2de1b60493721cdf6cd0f25933c702c9f25f87bc6dc735347 is not running
Error response from daemon: Cannot kill container: e068a292b5e1: Container e068a292b5e1a59e9e8cc2a112c3f8919a265b8671f693a05e8cc6b41ffefb89 is not running
Error response from daemon: Cannot kill container: 09fe8732e1a4: Container 09fe8732e1a40eb53bcd840ed0bdf5237209337eecc623818b188ad466f0ddb1 is not running
Error response from daemon: Cannot kill container: 6c465a4eb78e: Container 6c465a4eb78e7b48dee4efdced3c5bb80bd2cab61a0c366f74fe88e62cbc9a30 is not running
Error response from daemon: Cannot kill container: b5706acdfa59: Container b5706acdfa5994330527c97e927807833ac7d950d4577fbd7c100e94d025ae3c is not running
Error response from daemon: Cannot kill container: 780f7b093793: Container 780f7b093793b4ff354dc2bf862130ed880ac8cc274d84b6cace0f4d86a5e175 is not running
Error response from daemon: Cannot kill container: fc61c0375020: Container fc61c0375020401e4212c4658f4b5afde1691ad15b2904796e0311f37cd9c829 is not running
Error response from daemon: Cannot kill container: c4c7ac6664c6: Container c4c7ac6664c6952e9d3e54755bbafeafe384020e8657c458d3d2ac856531744c is not running
Error response from daemon: Cannot kill container: 625f310b5505: Container 625f310b5505e3f33d9ab97c02d405c144b6028d34beacca3d243addb04cc079 is not running
Error response from daemon: Cannot kill container: a55b7b850f23: Container a55b7b850f23b451f84fb0b44c460189fa508b39b77efc77969d9a66c3ed252f is not running
Error response from daemon: Cannot kill container: 9c4ef09b55fb: Container 9c4ef09b55fb02abd507f94e3c82fa6eaa69c556a940012df0e47d254a92b016 is not running
Error response from daemon: Cannot kill container: 027b43ecda6b: Container 027b43ecda6bb1dd4fb8e8e4ead0f308db7217e9d3ad39b2b293ef3c7811d562 is not running
Error response from daemon: Cannot kill container: 8b01cb37c99a: Container 8b01cb37c99a525cdc0cf9e342c5a9a228e24b20baec20ade0c213188a2307dc is not running
Error response from daemon: Cannot kill container: 096df92b0661: Container 096df92b06614a97934a417ffb5576fe93460c99d135f7e4c0d2ad172d113dd7 is not running