GUI acceptance tests using environment deployed from packages.

Build: #2096 failed

Job: Onezone providers basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
10 minutes
Revision
55bf187d0d4ebfece7f274afc16ccd4ba4d3d0b1
Total tests
8
Successful since
#2082 ()

Tests

  • 8 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  44314      0 --:--:-- --:--:-- --:--:-- 44314
Error response from daemon: Cannot kill container: 3edf30f73200: Container 3edf30f7320078ea4f642d4f611c3063a254a91519f90e915003cc1b19e1fa3e 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-COPBT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COPBT/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-COPBT/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-COPBT/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-COPBT/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
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
W0412 10:07:37.563725     495 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  43083      0 --:--:-- --:--:-- --:--:-- 43083
Error response from daemon: Cannot kill container: b4c30f75a5f1: Container b4c30f75a5f181c956aaf2ab77891207b90e3f96ef50e4b571180c5f59053edb is not running
Error response from daemon: Cannot kill container: fa0f669690b5: Container fa0f669690b5e985d1112270324450c0f50184faf2cca4f42e6e984dadc67def is not running
Error response from daemon: Cannot kill container: 1a19c2a57148: Container 1a19c2a5714818f81bfa51865416258875253a3b07a97df06e16b353e0f3b821 is not running
Error response from daemon: Cannot kill container: b7dc652809da: Container b7dc652809daafe76889f9a8ea6841ce9453bf683970da2d774f0af7bd0920d0 is not running
Error response from daemon: Cannot kill container: 70aa3817aa69: Container 70aa3817aa69378c843833b5ebd23079cd67a4f490d5797ccdcb0b24898bc3ef is not running
Error response from daemon: Cannot kill container: a86b7cbda799: Container a86b7cbda7991ab0cdc01097c28c1012a4ad8efba172109af020ca59a284b693 is not running
Error response from daemon: Cannot kill container: 915b1aa4b196: Container 915b1aa4b1963bbd8ac740efe3c63e15c1968dde59a352b4c3fbd54e32519482 is not running
Error response from daemon: Cannot kill container: 72bf4347c2e8: Container 72bf4347c2e86ebdb2d220a5e854baaeb397c496d43e4e2ebf7e4bdc29dd0897 is not running
Error response from daemon: Cannot kill container: 4a9660485ae8: Container 4a9660485ae8b05a2ea8cce6337cb34e26d967e7d030030fd4369c90ef2385f2 is not running
Error response from daemon: Cannot kill container: 50b8e9b863ef: Container 50b8e9b863ef94847bcd1f9f17b120faaa5bb28a18e7290d756b88ad0b81f8c4 is not running
Error response from daemon: Cannot kill container: 1cbd6e58c67d: Container 1cbd6e58c67d5e11aa0867e9b2e11b232aadd5f3a9ab5db5b8e62011bd922051 is not running
Error response from daemon: Cannot kill container: 0cf1f4879935: Container 0cf1f487993533af4f9eb9d8d30167da32b3fbac8132f6c01870f1467eff1a36 is not running
Error response from daemon: Cannot kill container: 981e3e32fc9d: Container 981e3e32fc9d6db36b6fe30823479ff57a6e296a19380d61ca8a904c4be729e2 is not running
Error response from daemon: Cannot kill container: b2df971e1194: Container b2df971e11947d0f43923c3d5539d2110a7391d09a571dde351d91014948f41b is not running
Error response from daemon: Cannot kill container: a6200f4d3f56: Container a6200f4d3f5610c78b343f47052671e93d4ab96a51fb350b2bb003a3814ffb1c is not running
Error response from daemon: Cannot kill container: c55da3dfc6da: Container c55da3dfc6daf6c72991f357e036d098a0acbe0fa0c049f6567f812031083ff6 is not running