GUI acceptance tests using environment deployed from packages.

Build: #2100 was successful

Job: Onezone tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
21 minutes
Revision
069664170b01b34f9742ffb53de1c68131c0e582
Total tests
8
Successful since
#1943 ()

Tests

  • 8 tests in total
  • 20 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  43083      0 --:--:-- --:--:-- --:--:-- 43083
Error response from daemon: Cannot kill container: bea50f003069: Container bea50f0030697ebeb42ca125a9be0ff8c774c9fc491c2093c74447233fc75ad0 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-COTT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/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-COTT/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-COTT/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-COTT/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]
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
W0414 00:58:10.002640     492 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  21742      0 --:--:-- --:--:-- --:--:-- 21641
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: c0e3b099c7a4: Container c0e3b099c7a4366a34d0dd0e63f15752329ebde614b40564ae04b4875f7b3c38 is not running
Error response from daemon: Cannot kill container: 55ebc451c332: Container 55ebc451c33279c957f20775f347a2260dfeb99a37c64cf572ce50ce239b9d12 is not running
Error response from daemon: Cannot kill container: 2ea7a0249acd: Container 2ea7a0249acd10f817fbb2c7fbb1027612aa6d6bd008570fdf84f01f5fd2bbf2 is not running
Error response from daemon: Cannot kill container: 426f00efdd73: Container 426f00efdd7308528a964b23aae93be03e123dde90cb082710d8388b283413eb is not running
Error response from daemon: Cannot kill container: a2438d73e9be: Container a2438d73e9bedf9ad73f67209956e321fa160224e8ea1878f2ac09a2c315c259 is not running
Error response from daemon: Cannot kill container: 3cd69f7a2f45: Container 3cd69f7a2f452daa42b7e5a71fab1f53c2150eaea96b62916f588763571f434e is not running
Error response from daemon: Cannot kill container: 239e31941ac4: Container 239e31941ac421c3ab6a6e88937eec6c1f1161b7d31727747f71f02999964fba is not running
Error response from daemon: Cannot kill container: 7967a88b650d: Container 7967a88b650d095246f629572b6b2074dc3a17d1fd39f45cb1fdb1509fe1cd01 is not running
Error response from daemon: Cannot kill container: 650ec4199809: Container 650ec41998094e7bdc4767144f4387299891cd90138ae7347bb6be0c4df3d929 is not running
Error response from daemon: Cannot kill container: 3bff66420b66: Container 3bff66420b66d25a45a8efc0ed80d65881b77509cd2b4c18df9c6589c1ac6a42 is not running
Error response from daemon: Cannot kill container: 757d8e536bc1: Container 757d8e536bc15a0459b947b67e97ea09a7ac89d5b2211a37aa2cbc6dacbd04e3 is not running
Error response from daemon: Cannot kill container: edc095b0fd6d: Container edc095b0fd6de97af4b02065442e7c33cb8ccf8f4aaea545a3b675c712c707d4 is not running
Error response from daemon: Cannot kill container: 7cf72b9bd807: Container 7cf72b9bd8073f491e0c2a5f6052c4c674089b32b1c4e67d89d19d22476d5760 is not running
Error response from daemon: Cannot kill container: 45482c60446f: Container 45482c60446f468807658e33616ecc5690a9fa62b0602b39ac83f2d821296edb is not running
Error response from daemon: Cannot kill container: 631a2c45b3f9: Container 631a2c45b3f918a1c45936ec9d6cb90ccfebb67a4f1a6d1fccd597018bc99672 is not running
Error response from daemon: Cannot kill container: 56920d7e3ee4: Container 56920d7e3ee4df2c763d9fec8bb19bc8778e2d615fc459ae1de5d2b20d39817e is not running
Error response from daemon: Cannot kill container: 22913aa15955: Container 22913aa15955011192c7adfc0577db1f6a655e518380ad4f9bc32554a8a36e77 is not running
Error response from daemon: Cannot kill container: e89c3084f50e: Container e89c3084f50ec0a0f6a0b88da8dc8d4befb2c044cc7e1005a3d4ec1ebd637446 is not running
Error response from daemon: Cannot kill container: 1c83d84a9719: Container 1c83d84a9719ec59eebfe2b27a4a4278507fc6882e61ae037a56c0cf1098df62 is not running
Error response from daemon: Cannot kill container: 9fb85279f9a3: Container 9fb85279f9a3af78a74905762d22f72227885e1c2e6f71c9d5ea08afb699b323 is not running