GUI acceptance tests using environment deployed from packages.

Build: #2183 failed

Job: Onezone harvesters effective privileges was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
16 minutes
Revision
3e03531a9135db305f145c67e729e44a9ecef612
Total tests
4
Successful since
#2110 ()

Tests

  • 4 tests in total
  • 14 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  43083      0 --:--:-- --:--:-- --:--:-- 43485
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: 3cf4347efe79: Container 3cf4347efe79e936700ae687dfaf12a0af5baa3e36c3a09dacb2f7a539d3f258 is not running
sudo: unable to resolve host bamboo-agent-amd-01-do-not-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-COHEP/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHEP/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHEP/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHEP/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHEP/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHEP/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-COHEP/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-COHEP/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-COHEP/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-amd-01-do-not-disable
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable
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]
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?
command terminated with exit code 126
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
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
W0627 18:53:59.126879     449 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  31439      0 --:--:-- --:--:-- --:--:-- 31439
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: 3c6695462130: Container 3c669546213031185157ebbb34baab8b0b95874819645f5cf8640f288e431cd9 is not running
Error response from daemon: Cannot kill container: d6279f6be7d8: Container d6279f6be7d87a506b7cbe22bde5a97483ecbd1f51f233e2e41f9ff6aa10b680 is not running
Error response from daemon: Cannot kill container: 98127c5140ec: Container 98127c5140ec1eb71eac1c5bb8092e2e21e27b2fc723fb5ad634f39481432555 is not running
Error response from daemon: Cannot kill container: 86550e6ab5a9: Container 86550e6ab5a9b076e3af9cbbc794770c1e59fe8566a5459de0edb009abf358fb is not running
Error response from daemon: Cannot kill container: da2bfa097e62: Container da2bfa097e62f8b1f02fd5b891515ce33f9bb8d9dd5e57ae7ef5400736e701a7 is not running
Error response from daemon: Cannot kill container: 7fc8c8bab70c: Container 7fc8c8bab70c9281f30ccfaa9c4c0b45d1a64753ecd9d5506b5d5328b63a0ef2 is not running
Error response from daemon: Cannot kill container: ca13443bb06e: Container ca13443bb06e5445cfd9604594ccb21874f66886a6479da535ea2d5c6a644930 is not running
Error response from daemon: Cannot kill container: 8c8e9a2feb0d: Container 8c8e9a2feb0dca203ca7c98fea380ad929d31ee23577dea489379808b2cc9f26 is not running
Error response from daemon: Cannot kill container: 1e6bf03d3f1b: Container 1e6bf03d3f1b2fd8b3afcd886996badded1db3e4b591e5b4bbfed3cc91e736a9 is not running
Error response from daemon: Cannot kill container: f280d07dc60b: Container f280d07dc60bb3e7919606b5eab7f92dc9f8670d2970b5ab0bf1582626e18687 is not running
Error response from daemon: Cannot kill container: 82fb69e83124: Container 82fb69e831246261d02603a578a435714d69ef6614fc5c9f7fa6e708e50327b2 is not running
Error response from daemon: Cannot kill container: c609469d1c50: Container c609469d1c50e8f7dcd41c99162f65af796ddd33b3d06e0febe5fb27f13afe5e is not running
Error response from daemon: Cannot kill container: 8905733ef395: Container 8905733ef395b3ea10246f87eef259c24c105813c686721d200d6fc876921a2e is not running
Error response from daemon: Cannot kill container: 7598287aba73: Container 7598287aba7368948911a72e50a03f91d147d865782950c1607136d6f4e10ed7 is not running
Error response from daemon: Cannot kill container: 97e85aa1f015: Container 97e85aa1f015e4665322fde1a69d8680d1d9023010bfd47d1b71e0f8e56b2818 is not running
Error response from daemon: Cannot kill container: bbe088c9cff7: Container bbe088c9cff709dd6f0088ae6e99238565929ed0724960ddfdd5c2c0c706bbb0 is not running