GUI acceptance tests using environment deployed from packages.

Build: #2010 was successful

Job: Onezone data discovery was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
29 minutes
Revision
ed4f134a7d934cf4803abda141850366f8511cb2
Total tests
17
Successful since
#1943 ()

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  48978      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: 4c58add0e701: Container 4c58add0e7011c40879f3a5a21d6359ba903155cefebbc70b8da6145b23aad1b 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-03-04 01:20:53,340 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-04 01:20:53,340 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-04 01:20:53,340 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-04 01:20:53,340 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-04 01:20:53,340 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-04 01:20:53,340 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-04 01:20:53,340 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-04 01:20:53,340 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-04 01:20:53,340 WARNING Connection pool is full, discarding connection: 127.0.0.1
2022-03-04 01:20:53,340 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
W0304 01:32:00.877899     440 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  43896      0 --:--:-- --:--:-- --:--:-- 43896
Error response from daemon: Cannot kill container: ecbf815c4f36: Container ecbf815c4f36bafcc83e99fff71eb3c4e993770eab7f459f649ad4c693001ef8 is not running
Error response from daemon: Cannot kill container: 3dce4e81d7db: Container 3dce4e81d7db45c4220be719f434c6a0acb773ee1a064fe35f6eb2b48b082e05 is not running
Error response from daemon: Cannot kill container: ce8cb244b2e5: Container ce8cb244b2e5b5fa033e0b0e9bcec6a2bf1b3e74db672e99ca4cd6d456ef6113 is not running
Error response from daemon: Cannot kill container: 8e54aaf73cbd: Container 8e54aaf73cbd0b81555ae808d8a28e5549086004729b40e7ee399facdb7253ba is not running
Error response from daemon: Cannot kill container: f5124dbb0a48: Container f5124dbb0a48cb3495b6aa8af0c09c552784988beccb0d5d821225041a2ef677 is not running
Error response from daemon: Cannot kill container: 22f1ac368748: Container 22f1ac368748f6209c53b6eeb08a8dad9f36b4bf0027c839f3b6e6abec9479c1 is not running
Error response from daemon: Cannot kill container: 371aed670445: Container 371aed6704459a40f5e6fdf31f015839a213f056a0b13242d69647c9b25246f0 is not running
Error response from daemon: Cannot kill container: 6abe1ce47241: Container 6abe1ce47241e1eeeeaa0b352a9f43a81723c32adf934418ab679c522871fabb is not running
Error response from daemon: Cannot kill container: 3a014c236dc0: Container 3a014c236dc082225f5a517508132d245989a37855544f08cef2d9f888321424 is not running
Error response from daemon: Cannot kill container: b00e2307cb61: Container b00e2307cb61b577bc44e4ebc67dc237496e6a3396fff103743aef834f968dc5 is not running
Error response from daemon: Cannot kill container: 2d9bb2f1684f: Container 2d9bb2f1684fc5e15b471a98fe374ef2e024e3718c085857dc94c7cbfbe73489 is not running
Error response from daemon: Cannot kill container: a5946fbe616a: Container a5946fbe616a89ded8cc53611711bc34220147bc16d5741db576af1475d6fc19 is not running
Error response from daemon: Cannot kill container: 35e71bea732a: Container 35e71bea732ab0fe75c564cdb183c09eeeff0de92fcaa40d5fe6609266e3aa70 is not running
Error response from daemon: Cannot kill container: fa936a90756c: Container fa936a90756c912d3b557e5b23f124349797132ae419611614d74504c9c66276 is not running
Error response from daemon: Cannot kill container: fdd1a3e62a88: Container fdd1a3e62a88f4532c4213a46e3130967ff2267e7d5814a07a606f29e2eb8d25 is not running
Error response from daemon: Cannot kill container: fee7461c4761: Container fee7461c4761e6a7619800bbb83e99014e053b0a92eb1052cf31bd0eb1085244 is not running