GUI acceptance tests using environment deployed from packages.

Build: #2042 was successful

Job: Onezone harvesters index was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
13 minutes
Revision
d4a37ebda8d9cad234b655aae75d29294552ebb5
Total tests
5
Successful since
#1958 ()

Tests

  • 5 tests in total
  • 12 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  49500      0 --:--:-- --:--:-- --:--:-- 49500
Error response from daemon: Cannot kill container: f86d27b1880c: Container f86d27b1880c1b7675a02126775bb87f6416cb0eafca495abd54d3ec48c62ff7 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-COHI/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/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-COHI/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-COHI/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-COHI/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
W0322 12:42:51.536515     436 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  23034      0 --:--:-- --:--:-- --:--:-- 22921
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 553472e8027e: Container 553472e8027eba62d93536219dd5843df9a842c8985e7320f6bfc02700e92925 is not running
Error response from daemon: Cannot kill container: 590b2a564f7c: Container 590b2a564f7c5b6e8b6f0f766858f0dca0c06877a52fc6c8406894f7cfe94957 is not running
Error response from daemon: Cannot kill container: 632b2f82fa0b: Container 632b2f82fa0be4dc953e0b0f595665dfc89057293a9ae5d20e51940dd6d567c6 is not running
Error response from daemon: Cannot kill container: 6e464ea8244d: Container 6e464ea8244d1140886a72976bb949b822521fc3968279b2a1a06bc3b79921ea is not running
Error response from daemon: Cannot kill container: 10ff59e53118: Container 10ff59e531188241fc6dcd98693e0ba70d708f7e02f6d6408b3b1e3bdfaca64f is not running
Error response from daemon: Cannot kill container: c2780a7cd394: Container c2780a7cd394dde0fa0a4b967f7cf29788a97f30a6990c61ed6bf3497f663aba is not running
Error response from daemon: Cannot kill container: c2a9c31dfdc0: Container c2a9c31dfdc0165bf19c66bf3ac0a7273a6ea27df7002244932eab992067d640 is not running
Error response from daemon: Cannot kill container: 864098909d9d: Container 864098909d9d8ea99a0812aa2069b4d8199f6c907bda6c1b0832a7be73e18d16 is not running
Error response from daemon: Cannot kill container: 39ff295d5de5: Container 39ff295d5de5ea62f42d47490407eebe266ce633e66fbbf679afb941323af54b is not running
Error response from daemon: Cannot kill container: ed6b404efd6e: Container ed6b404efd6eecc026b9a80ab118bc7209cb2e738d07e918fd57bd80d79c7aec is not running
Error response from daemon: Cannot kill container: 2587caea14aa: Container 2587caea14aa37299a23cba98fa545e6a5a94c3d6e9418bc7c0702f3ccd82a79 is not running
Error response from daemon: Cannot kill container: b4fdcf912e86: Container b4fdcf912e86a5b5eca47507973569d0f000e1c6bde989fd8adce7db827f4160 is not running
Error response from daemon: Cannot kill container: e92e91960821: Container e92e91960821a452a75e894ae717c75031c3bbada8b73184e4377eb6ff9ad1c6 is not running
Error response from daemon: Cannot kill container: 45d097de6b82: Container 45d097de6b82c5a0c8df5e1b2f912128532070de9cc2e8bc3b4147d21c664435 is not running
Error response from daemon: Cannot kill container: 98d5042f821f: Container 98d5042f821f91238125874403c1b975a7d7bbf900237cbe72d9c5a7868ab831 is not running
Error response from daemon: Cannot kill container: c6aa9631e19a: Container c6aa9631e19a2f423417d93f3991c5651510c4c3c6d721f0cdd59c74820c72e1 is not running