GUI acceptance tests using environment deployed from packages.

Build: #2132 failed

Job: Oneprovider archives incremental and nested was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
24 minutes
Revision
39fb434fa4268b56f32dccaa52527f3591cd9ea8
Total tests
8
Successful since
#2108 ()

Tests

  • 8 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
100  4653  100  4653    0     0  41544      0 --:--:-- --:--:-- --:--:-- 41918
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: 6c455ee59332: Container 6c455ee593320d5afed1ca8f89671299e1922340ef3077657c7fd1964c2fc0d3 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-COAIN/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/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-COAIN/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-COAIN/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-COAIN/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
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
W0505 23:29:21.479909     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
100  4653  100  4653    0     0  18914      0 --:--:-- --:--:-- --:--:-- 18914
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: d383db45fd31: Container d383db45fd31a6dbfe123d9c33fa101c36e6e2fc2feb47e9c96e25be31f9f522 is not running
Error response from daemon: Cannot kill container: 9f2adc83e3d1: Container 9f2adc83e3d12c40a7c127e5bc9a06f9ce91d0e28849f7776e2804a0febdddfd is not running
Error response from daemon: Cannot kill container: 0c4f1cb5d3ca: Container 0c4f1cb5d3ca860ffd8fbcda179fc1ebaf9a3ec4bec9e00647e6db113db345b3 is not running
Error response from daemon: Cannot kill container: fbab32e3026f: Container fbab32e3026f9ea4600d1df348f9c2f797d06dd4a7a2ff499bd1eba551d81a28 is not running
Error response from daemon: Cannot kill container: 66b464109708: Container 66b46410970848eb75cf693aa1e35c480ceb1d9640a60652c708292138d17c87 is not running
Error response from daemon: Cannot kill container: afb90f673d0b: Container afb90f673d0b38fbcb3a94524aa9e078402969b973b891b4900ac9eb5abdf249 is not running
Error response from daemon: Cannot kill container: dd0bea6d7dbd: Container dd0bea6d7dbded7360910ffc25ce4079a4bb00b35856575ebd8fd984396a7604 is not running
Error response from daemon: Cannot kill container: b636c28a11bb: Container b636c28a11bb90789d0b9ad31fd4600f1ffdbd94be946b108fc12b589a8d6707 is not running
Error response from daemon: Cannot kill container: bdd8b35e028a: Container bdd8b35e028ae6ce80c8fa64b3b7ed706e3bae45deaf9a5ed8cefb83610129fe is not running
Error response from daemon: Cannot kill container: 7060be403db0: Container 7060be403db0c7c75ea75a111eafd07559bed8d6af5c99df74f2c1f9b560ea6c is not running
Error response from daemon: Cannot kill container: da17589256db: Container da17589256dbd7a0fb1bd4bf386c15b5596ddad6dc3f1968f18211c9c5a33dcd is not running
Error response from daemon: Cannot kill container: ce355f8b63b3: Container ce355f8b63b332d9a7d89bd8498d2a3555b79911a3b8fee898dd9278487f3ba9 is not running
Error response from daemon: Cannot kill container: 348c2bc6b1c0: Container 348c2bc6b1c0714a3ca6d02adb1d20268b84f3cf0da44d2f66590427297de3f5 is not running
Error response from daemon: Cannot kill container: 2642eea91f6a: Container 2642eea91f6a475790a6af0023cc1c054048dd1171f48a1633af252f513bb353 is not running
Error response from daemon: Cannot kill container: 7e81b96ec111: Container 7e81b96ec1113900ff7720697cade91da565ed91b195811d849dcef9ea0c52d0 is not running
Error response from daemon: Cannot kill container: 2d5612716ecc: Container 2d5612716ecc642e8389660029d11da084ee1ef5c94c33f5da2fdd22f3a2a5d7 is not running