GUI acceptance tests using environment deployed from packages.

Build: #2103 was successful

Job: Onezone invite tokens with caveats was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
10 minutes
Revision
90fc7afe3680c7ff2b4e3e422371d0941ed8ee84
Total tests
4
Successful since
#1958 ()

Tests

  • 4 tests in total
  • 9 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  47000      0 --:--:-- --:--:-- --:--:-- 47000
Error response from daemon: Cannot kill container: 47f0c5592538: Container 47f0c5592538c6699f962da4ed66aa201cc6d37eb17029bae672f704e0bc2949 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-COITWC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/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-COITWC/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-COITWC/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-COITWC/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
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
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]
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
W0414 14:11:18.722020     494 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  39432      0 --:--:-- --:--:-- --:--:-- 39100
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 5e86cc48ccc4: Container 5e86cc48ccc49caac68a5df6d801966be564be3f6e59cb0cbc1222e163907ce5 is not running
Error response from daemon: Cannot kill container: 2ae285cfbafa: Container 2ae285cfbafafe8a98942ace1416253e5689936c64ce5fb808c4ea320f62469d is not running
Error response from daemon: Cannot kill container: 0eb50d9af3ce: Container 0eb50d9af3ceeb780efb12d07ce5e48995fe687c49058d32f923fe2e7f2c8886 is not running
Error response from daemon: Cannot kill container: 691c50381ae4: Container 691c50381ae48fff01758921449866b0249a346b97164eec9bf19bc3b903a557 is not running
Error response from daemon: Cannot kill container: 7ac2b626da56: Container 7ac2b626da56a6f47e095c6bba6c23ee9fad707a4b09b3f67d71e605b36a6671 is not running
Error response from daemon: Cannot kill container: 14fa6c56bca8: Container 14fa6c56bca8eef22c2c979d9c656d49bf3669a8bb710e22733cbfb78826901b is not running
Error response from daemon: Cannot kill container: abfa413c7672: Container abfa413c7672e4e7587db2f85890c4a93ab10f47a6f7779add944e1ab79f7b3a is not running
Error response from daemon: Cannot kill container: 4b682d8cc929: Container 4b682d8cc929a3f66c2f94681d79011a4e712ce9d1e8691f3fc4189de11d4293 is not running
Error response from daemon: Cannot kill container: 9d4f1ac865aa: Container 9d4f1ac865aa6215e2670773d3ebca300c05d800561a54662dfbb64b93492aa4 is not running
Error response from daemon: Cannot kill container: 916789fd9975: Container 916789fd99754bd649b9111756be25c0452c42ec8126b98da20d57105b344f52 is not running
Error response from daemon: Cannot kill container: 1dcb2a8f7cf6: Container 1dcb2a8f7cf6df464c46b56cf29e6be6ed31d7a10a8a2acb8b4d17dc38e96797 is not running
Error response from daemon: Cannot kill container: 3a5d73ff6a02: Container 3a5d73ff6a02852a4ff85bea70841488c42af1688c9ac172719756fe95d58164 is not running
Error response from daemon: Cannot kill container: ac4f6c0a7176: Container ac4f6c0a7176ad932ec7670ae7a05165142a7308ce7182b616dc604c493eaee0 is not running
Error response from daemon: Cannot kill container: 322916150db1: Container 322916150db1b89f1fbab427da49c436972c177fb32c5154d7871763b7f54fb7 is not running
Error response from daemon: Cannot kill container: 1e255fbdff57: Container 1e255fbdff57916f00730e1db9a2e2c170f7e58eb1195897ffb2b5e7e1a3b96e is not running
Error response from daemon: Cannot kill container: c3a6a64ecf36: Container c3a6a64ecf36239b57e401ca415e27d249976fbb933a814367d7b2d5e4a6c9bf is not running
Error response from daemon: Cannot kill container: 13fcd13efea2: Container 13fcd13efea2f6fb4d22dbda48e4b0dbd1fd7bf4fc11f9e713959a078c79b227 is not running
Error response from daemon: Cannot kill container: 45c883b69d1f: Container 45c883b69d1f45c5f0e584750feb6a811c1bf130b2cfa9c1880de63820c84036 is not running
Error response from daemon: Cannot kill container: b73175554966: Container b731755549668b5baf84f1d92ce39312036635dc5f1cb70a61348c8aa082b54c is not running
Error response from daemon: Cannot kill container: 7a897bf2d64b: Container 7a897bf2d64bf13a011244cc098b181f51bb6e7899303d0ba463780674ee1685 is not running