GUI acceptance tests using environment deployed from packages.

Build: #2178 failed

Job: Onezone spaces multiuser was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
16 minutes
Revision
8046c81cb26d07683c2acee37fe8f6bde9d9a654
Total tests
13
Successful since
#2113 ()

Tests

  • 13 tests in total
  • 15 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  46069      0 --:--:-- --:--:-- --:--:-- 46069
Error response from daemon: Cannot kill container: d9e8936a3d8e: Container d9e8936a3d8e39bea21bea569193f3312f5f464b0287a7a29abe9605eb564c75 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-COSMT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COSMT/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-COSMT/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-COSMT/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-COSMT/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
W0620 10:35:26.180354     446 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  46530      0 --:--:-- --:--:-- --:--:-- 46530
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 6cf0b26d79b1: Container 6cf0b26d79b156260a6c9826d57022573c4ba00897053f20b5eb60c6acf8c511 is not running
Error response from daemon: Cannot kill container: 910f2e3ec145: Container 910f2e3ec14587120932af6f7f574f57e4ebf0730f1a5f9f21cdd240d91ca287 is not running
Error response from daemon: Cannot kill container: 4f3f368d0d68: Container 4f3f368d0d6896ad482a54fc70b1259ee04165b6ef8aa1cef4f12cbecd3e5f84 is not running
Error response from daemon: Cannot kill container: 81be79c122c4: Container 81be79c122c44f391225b91e37304875f40cf623ca43429d41d907f9bff70875 is not running
Error response from daemon: Cannot kill container: 2348c148d17d: Container 2348c148d17d3962aebc92e958ac0794eda0303e7150d4648fa87a75ba783f52 is not running
Error response from daemon: Cannot kill container: ea7b9a6e707c: Container ea7b9a6e707c9f490b27790e1e53d618f39ee65c763049fd4ec3e3ed46077548 is not running
Error response from daemon: Cannot kill container: 82b093798de0: Container 82b093798de08d63d763d9c625a7eab9d32c4fa4116d628691fdc49ae02d3d77 is not running
Error response from daemon: Cannot kill container: 69bd200e20d1: Container 69bd200e20d1f4b3cceed15f8bde1b316edeb96cb702a1444316bebf4c83e61b is not running
Error response from daemon: Cannot kill container: e175eeea869c: Container e175eeea869c9cb2f459aee8491496e70a0a50fb50acee1518953b1834394855 is not running
Error response from daemon: Cannot kill container: 061699ccccb6: Container 061699ccccb61c85edffb923d801e0486204e942c61313e48566fd1192eaac11 is not running
Error response from daemon: Cannot kill container: 40f0f8bd931c: Container 40f0f8bd931cee1447c1ab172020759585f3e776d27589556dfe3fd6210ef288 is not running
Error response from daemon: Cannot kill container: e3c9b34390da: Container e3c9b34390da572ca08b878fc45815dd1e9e8067640021adcfb854dcbf4d8c0c is not running
Error response from daemon: Cannot kill container: dfd9b969e886: Container dfd9b969e8866e881364e2127409d4f7fc4f182f86c7bc507fc7b9469904584d is not running
Error response from daemon: Cannot kill container: 63ad3d9db123: Container 63ad3d9db12341f58438616d018056503f7cfd96e405ab66e6579b07f6b33f1a is not running
Error response from daemon: Cannot kill container: f64cebdd98d3: Container f64cebdd98d3553ed7b4df191d190daa60c2eb3710dd13fa696c243a6e1bac0d is not running
Error response from daemon: Cannot kill container: c320476e8f58: Container c320476e8f58441145d42ee025504bafbc8fe8644f1396600a9ff6315337ea99 is not running