GUI acceptance tests using environment deployed from packages.

Build: #2193 failed

Job: Onezone data discovery helpers was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
8 minutes
Revision
466b4a1341ba42e3ce27e138642da6627c86d0c6
Total tests
4
Successful since
#1958 ()

Tests

  • 4 tests in total
  • 7 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
Error response from daemon: Cannot kill container: c846015aca0c: Container c846015aca0c49159234ffcfaf7f991bd82fdb5bf6f3dd109bab36b798f10469 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-CODDH/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDH/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDH/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDH/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDH/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDH/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-CODDH/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-CODDH/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-CODDH/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
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
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
W0701 01:07:38.316862     445 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  43083      0 --:--:-- --:--:-- --:--:-- 42688
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 654e46a8df12: Container 654e46a8df12da8a5f9adcf720360938291ee6b49a58ec83b76537bd4e1c9d44 is not running
Error response from daemon: Cannot kill container: 5b64597bc387: Container 5b64597bc38798fb7fe9f125a935122cb74ea805a9cc2c7f7cf3ccf2277f6ac1 is not running
Error response from daemon: Cannot kill container: 214820e17743: Container 214820e177431c0accc32ec078e5bada6fc5cc4d3e39b354782defb142cc5b79 is not running
Error response from daemon: Cannot kill container: f020129354e0: Container f020129354e07f15d85274ee6d9e06cb6f9cce2fd323448acae0ede8967d0f54 is not running
Error response from daemon: Cannot kill container: 32058c7d45f1: Container 32058c7d45f1086adb7516232992d725c3d3de9026629f9bb4aed0efba6db617 is not running
Error response from daemon: Cannot kill container: d3805e891f40: Container d3805e891f40eb081078a84c4254ea1bd12b2991b4c4796ec74450053645dcee is not running
Error response from daemon: Cannot kill container: aeb43c84b4de: Container aeb43c84b4de92d9e18e726dba95df1d01dc95ee71e6f3f591de7bc6ec47fa72 is not running
Error response from daemon: Cannot kill container: d0eb974c78f4: Container d0eb974c78f4025d1251cc63a948c58c6dcf987fad9940602284c4e0a746cd9b is not running
Error response from daemon: Cannot kill container: 9a38d9ff24b8: Container 9a38d9ff24b820847e7d19ff6e6e1a734ff70e35dc5c5a2204706c48aaec3fac is not running
Error response from daemon: Cannot kill container: e99ada563560: Container e99ada5635601b54658fdbd37cf47e2bc82c83973e5808e085713f526e60e440 is not running
Error response from daemon: Cannot kill container: 7d0ccc28ba49: Container 7d0ccc28ba49b42b495043a854a9cdb1c57e7873126f8368da00616267957579 is not running
Error response from daemon: Cannot kill container: 4f6e5024ff47: Container 4f6e5024ff477f4ffbce3474782c5fbbdb5b91eb5b19098f75ce57675e23a617 is not running
Error response from daemon: Cannot kill container: fa1e13cd5d72: Container fa1e13cd5d72210dfce14f74abb4b7494d32bc931d8fa82b508130b04024628e is not running
Error response from daemon: Cannot kill container: 4d4f43bdf490: Container 4d4f43bdf49064fe1ecef4d20b424b734f8a01839afd6988bf54445b55eb5654 is not running
Error response from daemon: Cannot kill container: 24e72c44ed12: Container 24e72c44ed123b0d27fdd0b91886da20fe419c0ce808ca88c74e186593f3ba3d is not running
Error response from daemon: Cannot kill container: 2c8e7f6b4758: Container 2c8e7f6b4758fe6f7516d982aebe8b6ab5675ff6e593af1324c79153f4481947 is not running