GUI acceptance tests using environment deployed from packages.

Build: #2006 failed

Job: Onezone invite tokens with caveats was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
11 minutes
Revision
0ab5f662c3ea6d31c3ccedd9a5babeeb1a2cc8bc
Total tests
4
Successful since
#1958 ()

Tests

  • 4 tests in total
  • 10 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  44740      0 --:--:-- --:--:-- --:--:-- 44740
Error response from daemon: Cannot kill container: 2b2f9bc7c138: Container 2b2f9bc7c138bf4960dcaa22477a89f8019ff550826078cc5bc5f8afb3f6d4f1 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]
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]
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
W0301 11:45:24.625293     504 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  38454      0 --:--:-- --:--:-- --:--:-- 38454
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 5a4663199adb: Container 5a4663199adb1320c5acaccd2694628219972751ab3794f57307e8f3e6aae104 is not running
Error response from daemon: Cannot kill container: abbf6681f60a: Container abbf6681f60af46fd2b4ead7e05a5c806d2ab5c4137af61ce52cb2157a16e14e is not running
Error response from daemon: Cannot kill container: b72b637117bc: Container b72b637117bc387687259d32e11bca0d98f37c44d41ea450f81e1d944750a47e is not running
Error response from daemon: Cannot kill container: 1c7a1a162ad3: Container 1c7a1a162ad37973e1217963fe25f140c614db11f7c99a0f7a161c8aecaf3207 is not running
Error response from daemon: Cannot kill container: 7af941d4dd24: Container 7af941d4dd248fed83f8afe8eaa9328ccce408a2b82f4aa558f28a3deb71f049 is not running
Error response from daemon: Cannot kill container: 68cfcd3ca404: Container 68cfcd3ca4044d60dafb132657137cb741a4c9dd830b67abf208d92cc488208e is not running
Error response from daemon: Cannot kill container: 622b89a5c5f7: Container 622b89a5c5f7cced487bb10fc5d0d3c17115824e7bbce239bf220881a6f3ef70 is not running
Error response from daemon: Cannot kill container: ad63c5610de5: Container ad63c5610de576d40afefefff6212f232b766e99fdb96e74efc5620dcfb663c6 is not running
Error response from daemon: Cannot kill container: afe081e25e1d: Container afe081e25e1d4d1e0a8d7ac1ccfde11717048dff2f76ac067271028960ffaae5 is not running
Error response from daemon: Cannot kill container: d73d51da7195: Container d73d51da7195cdc940c1c5809e2dd7a5b27e6e9535c51d96fb1b28089e95eaa6 is not running
Error response from daemon: Cannot kill container: ff604d48cae2: Container ff604d48cae27a7592af9038aeda92a0c37aa099329d1abddbdaf386ec6234c6 is not running
Error response from daemon: Cannot kill container: e6cf45e02fac: Container e6cf45e02facd9e03f6c75965406e1dff22ca53bc9988e3312dca16cf2250e95 is not running
Error response from daemon: Cannot kill container: e5c3cb2dcbd0: Container e5c3cb2dcbd08bbc9445834785bb27905ddfe672806f0dfb7a0f28a84d180f76 is not running
Error response from daemon: Cannot kill container: 38aa3a9661d8: Container 38aa3a9661d8ab1bba5bc2a6d89f66f10b1eb0ee24b73c513529e08813d9fa4d is not running
Error response from daemon: Cannot kill container: 99c73792f1e1: Container 99c73792f1e1a4993985af98fd696c1d4aabb72b17102747a1c08982039632fb is not running
Error response from daemon: Cannot kill container: cd401e5cb540: Container cd401e5cb54080bedd9df842cd0183e41feccd3537a8840120a859cd512e8393 is not running
Error response from daemon: Cannot kill container: a36f35c5e51c: Container a36f35c5e51c50e0505fb106c99e43ee19f3c5c24a54be6a47ed920327397ff0 is not running
Error response from daemon: Cannot kill container: ba98f5f85d72: Container ba98f5f85d7283ec38bd05cf792e0f058e844a5d29327bcda065817623827e17 is not running
Error response from daemon: Cannot kill container: 5f0b5e15be64: Container 5f0b5e15be64eb3c8d806de9c2ff29b93c404f6f0f8816bc693674f798f4abb1 is not running
Error response from daemon: Cannot kill container: d1c70de15d5e: Container d1c70de15d5ec65ab3969677ba479e50339aa3434bfba629d3b68f4c969db449 is not running