GUI acceptance tests using environment deployed from packages.

Build: #2112 failed

Job: POSIX multiuser was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
12 minutes
Revision
d6888cd402c1e2c666417f7e0c3bb45e62d1469e
Total tests
8
Successful since
#1943 ()

Tests

  • 8 tests in total
  • 11 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  47479      0 --:--:-- --:--:-- --:--:-- 47000
Error response from daemon: Cannot kill container: 75059b67f2c8: Container 75059b67f2c8ef81f494b20ab93e3dc3d7a06d007be89a6041639a5c80e1d672 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-CPTM/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/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-CPTM/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-CPTM/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-CPTM/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
W0421 08:52:05.860403     437 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
  % 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: a65d239dbaf4: Container a65d239dbaf4f727fa00815638c5f27e83476a57a0bc29ec046ab94a86b1a988 is not running
Error response from daemon: Cannot kill container: 33e6338a7bc5: Container 33e6338a7bc5420ce7295b247a9b23f68ee736779ba7ba051920ead1024cfab2 is not running
Error response from daemon: Cannot kill container: 330442c9213d: Container 330442c9213dc16ba9922c99a281b69664fdf6e2f1b81824fe6b05c263d90cb2 is not running
Error response from daemon: Cannot kill container: 1f9abcf01fa0: Container 1f9abcf01fa09a6bd3b843248d5e153849d0efac5dbb721cb3d3b8c93107d892 is not running
Error response from daemon: Cannot kill container: 0a135045a84b: Container 0a135045a84bf095f45bca95dd4c079b6bd1241a1ab3b68783fad2a46d7bac91 is not running
Error response from daemon: Cannot kill container: f6d419c06e68: Container f6d419c06e682b8609c44b7d27d3a40ed65fc7e33c49c370b56a6b20019fc841 is not running
Error response from daemon: Cannot kill container: fed28bc9daa1: Container fed28bc9daa12340d225bde5b9a84eb870cb8345d90fde6118617459df8483cc is not running
Error response from daemon: Cannot kill container: 2907b4b79c69: Container 2907b4b79c69e3e1093dbe24cf1d8e2135fae7322d85570f1434e2ab82cc766d is not running
Error response from daemon: Cannot kill container: 2da5311eda2e: Container 2da5311eda2ec5818a78429ffac86a4995a9668bde95dc646e679371534e6361 is not running
Error response from daemon: Cannot kill container: b61e7427852d: Container b61e7427852d9b5eaa065e1bc3d94319a37bf565e338013eb0938b1d95baa29d is not running
Error response from daemon: Cannot kill container: d13acf238a44: Container d13acf238a44619c33d6ee9527d49ec6de322c3ddafcaa9264e1c5d311ae7fff is not running
Error response from daemon: Cannot kill container: a3c8de71366c: Container a3c8de71366c657265abc8a03bc6fad71268d7344779b0b015ab7f98772c8a56 is not running
Error response from daemon: Cannot kill container: 93db5ca0ecde: Container 93db5ca0ecde0fac0e5b348515f0d640864f2da6113b37103985841be9b03bb0 is not running
Error response from daemon: Cannot kill container: b7c0dc8706b5: Container b7c0dc8706b52e2a4098a599b9ead73f050f69b58091cebe4f8ccc9ff89ee70c is not running
Error response from daemon: Cannot kill container: c90b822077b8: Container c90b822077b8333c8a12d9f421e8fbc2a02b918681cd126024391e158c8e30e7 is not running
Error response from daemon: Cannot kill container: 2d1d1be7159c: Container 2d1d1be7159c9d4d0e87ed26a2dd22373337c9ce65d403fc5aafe6aaf0cccdd2 is not running