GUI acceptance tests using environment deployed from packages.

Build: #2121 was successful

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
28 minutes
Revision
531283e2b89b3833269b775ff1b3609165404e1a
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  45174      0 --:--:-- --:--:-- --:--:-- 45174
Error response from daemon: Cannot kill container: 3a0380bf1fb0: Container 3a0380bf1fb066226ae2cb3dd5e0131eae5d46af515c3cfcfcc93ffad7460b0e 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-04-26 20:35:13,581 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-26 20:35:13,581 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-26 20:35:13,581 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-26 20:35:13,581 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-26 20:35:13,581 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-26 20:35:13,581 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-26 20:35:13,581 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-26 20:35:13,581 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-26 20:35:13,581 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-04-26 20:35:13,581 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
W0426 20:46:26.741288     444 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  46069      0 --:--:-- --:--:-- --:--:-- 46069
Error response from daemon: Cannot kill container: ce404dd0fcab: Container ce404dd0fcab67669d9368df64113e6d86b16cadb584b85450558c2285b23792 is not running
Error response from daemon: Cannot kill container: b86e1921505f: Container b86e1921505fea302a562c2230edf427263c38f4bb71fa477e986461481608db is not running
Error response from daemon: Cannot kill container: 06db35774924: Container 06db35774924f16c9c3b16a0ff5b15a9dd16597a91040f7fa78463431ad84836 is not running
Error response from daemon: Cannot kill container: 6d678e6978ce: Container 6d678e6978ce39e1e35c93953d88232e97cdd2eb31247652864a19fdd34ebe52 is not running
Error response from daemon: Cannot kill container: 2f861ad5640a: Container 2f861ad5640a6a8602177b0134e1a3923508e015eeab4d2c8aa481bddf67400b is not running
Error response from daemon: Cannot kill container: 569576000c34: Container 569576000c34b84c1ce3e862f36c280683e411c7cf5ebe0d49894958ec25fd64 is not running
Error response from daemon: Cannot kill container: c2eb1b67d4d4: Container c2eb1b67d4d4012fe38e3a9198189d8142ef8a3f403e5b1e7f98bba258f07b58 is not running
Error response from daemon: Cannot kill container: 1db326917601: Container 1db326917601de42c1737505745cb82990c9f589a51cda2c31c9b39cb0b0c479 is not running
Error response from daemon: Cannot kill container: e6c2a76190c6: Container e6c2a76190c680c391d16783746e5544682349e73f16cda5f5c6f4f30f4b3902 is not running
Error response from daemon: Cannot kill container: cfd87a8f0080: Container cfd87a8f00801d74b53c960c6ac5074e1313e22361c0d2626ae1a3697a5c0a61 is not running
Error response from daemon: Cannot kill container: 432c1b6eadec: Container 432c1b6eadecfe8632885c43d4962c09b01ec40b38f5a263da9bc24582d9c749 is not running
Error response from daemon: Cannot kill container: ff83c92846cd: Container ff83c92846cda07d409925c78a2341d9453d2386a1530076fe5574523f7335df is not running
Error response from daemon: Cannot kill container: 1e81ebe0608a: Container 1e81ebe0608a6c39abab682a9e83addb20dd76fb613d936d77acbc32ed894007 is not running
Error response from daemon: Cannot kill container: 2a8c7db2adb6: Container 2a8c7db2adb6134b4ffd3ed01e4d8c578a7cba6c6ee17891b736ba0f61067ea9 is not running
Error response from daemon: Cannot kill container: 30838d8323fe: Container 30838d8323fedc1348b5ce13b7c5d3c48f4cfae3b9a2bf36df90190b2b52272a is not running
Error response from daemon: Cannot kill container: 86b09315d20d: Container 86b09315d20d5315d56fd9bdba6b41a54fe5547db7b1001c2c541f5f8bed0004 is not running