GUI acceptance tests using environment deployed from packages.

Build: #2143 was successful

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
27 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
Total tests
17
Successful since
#2113 ()

Tests

  • 17 tests in total
  • 27 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  50032      0 --:--:-- --:--:-- --:--:-- 50032
Error response from daemon: Cannot kill container: a4ea089c8d5c: Container a4ea089c8d5c52afa3ca574c839c53ff7bdf746b534d3aa545b25149c625c812 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-CODDT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/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-CODDT/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-CODDT/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-CODDT/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Unable to find image 'onedata/acceptance_gui:v8' locally
v8: Pulling from onedata/acceptance_gui
a1298f4ce990: Already exists
04a3282d9c4b: Already exists
9b0d3db6dc03: Already exists
8269c605f3f1: Already exists
c810ae7364ef: Already exists
78d356e6ec21: Already exists
792b20546d07: Already exists
c1d3130a77b3: Already exists
0c7ad6b015da: Already exists
114ec36e4007: Already exists
2bc588dde0c7: Already exists
89641d7ca7e2: Already exists
b6cd4b44aa19: Already exists
e1c77802a505: Already exists
f373aa611054: Already exists
Digest: sha256:97e4de524ef380ad8c07bf6c71280c378a5e0179834942ff0e6c0007d32b148c
Status: Downloaded newer image for onedata/acceptance_gui:v8
Error: could not find tiller
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
2022-05-18 20:32:48,052 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-18 20:32:48,052 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-18 20:32:48,052 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-18 20:32:48,052 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-18 20:32:48,052 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-18 20:32:48,052 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-18 20:32:48,052 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-18 20:32:48,052 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-18 20:32:48,052 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-05-18 20:32:48,052 WARNING Connection pool is full, discarding connection: 127.0.0.1
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
W0518 20:43:29.711321     435 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  44740      0 --:--:-- --:--:-- --:--:-- 44740
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: ab6e5e1727ba: Container ab6e5e1727ba08878e00b45ad4056ae76fba82643c3451ab7ba3d28f11dfd030 is not running
Error response from daemon: Cannot kill container: 419978a05f05: Container 419978a05f0509c472d90d5b2e1b88e796df615fd30c6b2a7451361ae552083a is not running
Error response from daemon: Cannot kill container: 71f4dee462de: Container 71f4dee462de25d851a837c545fd752667c1116983a760f3760fe388070c0878 is not running
Error response from daemon: Cannot kill container: e024465075d7: Container e024465075d7940260c5f7cd660991c5017d040de2bba16d4216bdb45d3b02c0 is not running
Error response from daemon: Cannot kill container: 6ace3c753d7b: Container 6ace3c753d7b468978fba202d79befe7ce60a4525b947813ff8a5d8eaa376828 is not running
Error response from daemon: Cannot kill container: 9365dada5a46: Container 9365dada5a46cbd11cda6082740db904627c60dc753f2724c07eb063587d9b75 is not running
Error response from daemon: Cannot kill container: eb6d2e509393: Container eb6d2e5093936e45f0da93ba69395966921ceec7e6578e6e0ec99def14ebdae0 is not running
Error response from daemon: Cannot kill container: 03d7e16b4c73: Container 03d7e16b4c732da456762a2d6a06bfb510607a5f0d93056582d004d4e0a977aa is not running
Error response from daemon: Cannot kill container: a42142a559bc: Container a42142a559bc2b98ed687af7156cab3f99ab86802a65d821a9a3c7425a01d9c0 is not running
Error response from daemon: Cannot kill container: f0bafc303dff: Container f0bafc303dffa1ca733134878c0093543355a11fee06539104032c3a2ce95c6d is not running
Error response from daemon: Cannot kill container: b951753f1d7b: Container b951753f1d7b1c4080b8ed0d56529a0103c3a89c5becdb750bed0bd410f472f1 is not running
Error response from daemon: Cannot kill container: 47b664f46596: Container 47b664f465964a48c311be9f1aa93dcb049290d81ae93461b906fe04dfa866ff is not running
Error response from daemon: Cannot kill container: 1ab73be63dae: Container 1ab73be63dae87cae3e5640b787403a28e3906e777cd1cf54520743d02ff0a49 is not running
Error response from daemon: Cannot kill container: cc8d4a7c12f0: Container cc8d4a7c12f0451d13133065092ed8c7cda603ada49066ac10eed05b58e6583f is not running
Error response from daemon: Cannot kill container: 9d9be9fe84a1: Container 9d9be9fe84a18a0e8023e8ae23e7ccd599df199f7e794cb76933eed71eb5754c is not running
Error response from daemon: Cannot kill container: 89ceae24704c: Container 89ceae24704cd68acb50848845173aaf02a1b48f4933bdb5f374d2d1f3d06cb4 is not running