GUI acceptance tests using environment deployed from packages.

Build: #2134 failed

Job: Onezone groups basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
23 minutes
Revision
72d4158537fcbe5e765cfeaf323ebd441ede24a2
Total tests
34
Successful since
#2082 ()

Tests

  • 34 tests in total
  • 22 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  50032      0 --:--:-- --:--:-- --:--:-- 49500
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: 5ab701ad8f34: Container 5ab701ad8f34a791f43f14cfcead72f1748916e640bcaeddcdbfcc02f26aea26 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-COGBT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COGBT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COGBT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COGBT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COGBT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COGBT/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-COGBT/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-COGBT/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-COGBT/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
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1006.0"
      after 15 requests (13 known processed) with 0 events remaining.
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
W0506 12:11:36.794980     440 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  47479      0 --:--:-- --:--:-- --:--:-- 47969
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: 9f0f8dcf7cb9: Container 9f0f8dcf7cb98a6163407bf7353f2308d90ee3e5babd3612cc85cee4e684ec8b is not running
Error response from daemon: Cannot kill container: 28c24f7cefe9: Container 28c24f7cefe9de8b3cafbe9b519920e52880d98afec70c9ce8e3fc2081d331db is not running
Error response from daemon: Cannot kill container: 79808262f816: Container 79808262f81611722b4520ad9df71b0f38c2d5de0e82b536e8e2e1f50cc78fc3 is not running
Error response from daemon: Cannot kill container: b9c9a6789692: Container b9c9a67896922ebb29c50b82908e961e7b7ef5650a9c59beb9016317958ef85b is not running
Error response from daemon: Cannot kill container: eafaf6aa15c1: Container eafaf6aa15c103456769fe399537dbf82df6e439be32eed7fd81c9963086cef2 is not running
Error response from daemon: Cannot kill container: a658e58bf95e: Container a658e58bf95eee6b5578905ec13bafb37fa51e745a3b71f428b0fc2527207f10 is not running
Error response from daemon: Cannot kill container: 847ec6f4d1a9: Container 847ec6f4d1a98dfe8418a47c74538cc41952193abf5c758a45e8ca6b6e60e9c7 is not running
Error response from daemon: Cannot kill container: 17250759ed52: Container 17250759ed520eef72a601d90bcf19098ab86dcf7cbe0e95edec49539a9014d1 is not running
Error response from daemon: Cannot kill container: a1a13992e9cb: Container a1a13992e9cbcd446db00a926c2bc6b0d8767a371d16353350ebd26d53a931f5 is not running
Error response from daemon: Cannot kill container: 2bcde4b7c1ea: Container 2bcde4b7c1eaa739ac39cd593f49f1f15916defcc3a37b15af89eac6cde71d91 is not running
Error response from daemon: Cannot kill container: eab05676163d: Container eab05676163de267cab9f885e104615e1d7233bc857784076b213393cf4de041 is not running
Error response from daemon: Cannot kill container: 0a1485f40062: Container 0a1485f4006236716065a4f2baba2f359960f8f430a871ff2ac75137db08b12e is not running
Error response from daemon: Cannot kill container: 1e8c2018cc0d: Container 1e8c2018cc0dd6c762e298c1b63a35b278ef22344ad6dee2bf288dc53055ec68 is not running
Error response from daemon: Cannot kill container: a2a2389148fa: Container a2a2389148fa760d3ca573a883e88101d1670e57f24902492c6489eb1f123831 is not running
Error response from daemon: Cannot kill container: a79db835e1b4: Container a79db835e1b44671e7db9f684002773bda637c989369719728c97581ed059c11 is not running
Error response from daemon: Cannot kill container: 23e0ec45d003: Container 23e0ec45d003a24e1c92031e612dd18f77bd04307bd6fb7ffc745ff7e235d384 is not running