GUI acceptance tests using environment deployed from packages.

Build: #2265 was successful

Job: Onezone automations was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
20 minutes
Revision
5049698a34395b30e4aeaf70b767f7a38cd18cb6
Total tests
8
Successful since
#2262 ()

Tests

  • 8 tests in total
  • 19 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  46530      0 --:--:-- --:--:-- --:--:-- 47000
Error response from daemon: Cannot kill container: e5ab701803ff: Container e5ab701803ffbcd91f95c8dc2adc56dfb98e610b2dd55e8a3422309eba2ad21d 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-COAT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAT/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-COAT/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-COAT/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-COAT/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
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]
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
W0817 20:55:59.350658     449 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  45617      0 --:--:-- --:--:-- --:--:-- 45617
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 5b53f83f436c: Container 5b53f83f436c5afb1b6ee65128b3f11b7ef5f0b54d0b92194ec42afb0274814b is not running
Error response from daemon: Cannot kill container: 2e9ccf998db1: Container 2e9ccf998db16c11f499e05cbae3b6a4be9fdabbe54e6ab540e4efa74289c815 is not running
Error response from daemon: Cannot kill container: 0be7295f5387: Container 0be7295f53870ff308b1ef022149d483fd7ae91bbf4160fe761840449ac73bfe is not running
Error response from daemon: Cannot kill container: 87c96c711231: Container 87c96c711231b56469e7262909c6a2a82e688e0ea9898dfecb60e547f2b85f29 is not running
Error response from daemon: Cannot kill container: 7a666b978c27: Container 7a666b978c27b6443b50dfa2397d79ce7d33cebd15ab6af36878a08ff48f260a is not running
Error response from daemon: Cannot kill container: 5b16944936c9: Container 5b16944936c94ef3c1637162d05406cd21601439c2bab8c24dc3755916059a79 is not running
Error response from daemon: Cannot kill container: e95616fb05b7: Container e95616fb05b7f884422bbb999e85469c9a9cefea27c9dab56d33e86e8d680445 is not running
Error response from daemon: Cannot kill container: 5d625f95470c: Container 5d625f95470cd8e12841cf6514d5256e2c83628877485bedee1e177b90442581 is not running
Error response from daemon: Cannot kill container: a3e08610cd24: Container a3e08610cd24bf9cdcb5ec14046c38be190f8a69fcbd91fc0c56cebacdb3b25b is not running
Error response from daemon: Cannot kill container: 8ed54885101c: Container 8ed54885101ca94ce966ed918203c307aa3902c2eed0e6a50eb2c31b16189a6a is not running
Error response from daemon: Cannot kill container: c67142f559c2: Container c67142f559c2b43dcbaaed70c0163ce04734fdbeca96a02551fb475eeea46f41 is not running
Error response from daemon: Cannot kill container: 98cb8e16b5d6: Container 98cb8e16b5d6e18d71b81aa75f6dd8516c21e82d094de540695b9f1981105821 is not running
Error response from daemon: Cannot kill container: 1d1fe2ffafa9: Container 1d1fe2ffafa99382e3baf6fc6fddf32de03093ec8e9b9b59eef4eee6c4cd4388 is not running
Error response from daemon: Cannot kill container: d306c31c156f: Container d306c31c156fa413e7eabb2d62d8db871f52a8f2dcd9918daed76620a9a12bde is not running
Error response from daemon: Cannot kill container: 0e244f7bda30: Container 0e244f7bda30a20e4d1527d850d47100b4e92e0a5f08005d8bb00a3c11817e84 is not running
Error response from daemon: Cannot kill container: c4c786a6703b: Container c4c786a6703b80900de1cea9ea7ce2eca713d7a48309f460c6d9fa7392b9f07e is not running