GUI acceptance tests using environment deployed from packages.

Build: #2147 failed

Job: Transfers files was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
21 minutes
Revision
55cdb7fe92fff892fdb8cf16f00c4ce6627a4c4a
Total tests
5
Successful since
#2028 ()

Tests

  • 5 tests in total
  • 2 tests were quarantined / skipped
  • 20 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  48978      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: d4899e444d70: Container d4899e444d703227edf02f0488b1514b430cf14cb1539d2e8b4eae5ac0df5b37 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-CTF/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTF/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTF/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTF/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTF/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTF/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-CTF/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-CTF/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-CTF/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
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
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
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  19227      0 --:--:-- --:--:-- --:--:-- 19227
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 72512b23e323: Container 72512b23e3232995eff163b41120ef4383e2ab2059fa61d2c6cbe2169c34fcdb is not running
Error response from daemon: Cannot kill container: a8d8cb1b6a2f: Container a8d8cb1b6a2f4e31e055bf1da68babf9f3a487279cb1e3de38fc86e3a781898a is not running
Error response from daemon: Cannot kill container: 27a0874730ab: Container 27a0874730ab47e049efdf31b5c3c882272ee5c2c483f1ebe50c43b456c79e8c is not running
Error response from daemon: Cannot kill container: b2be34fb6e76: Container b2be34fb6e76ad4d8747d888adfabec856f4010bee5cd73e40affe879cef820f is not running
Error response from daemon: Cannot kill container: 28e5db992761: Container 28e5db992761e1a68ba5dd74305fe97fc6c426d9d4b378d90eace78d60eafc8e is not running
Error response from daemon: Cannot kill container: 09653e2a221b: Container 09653e2a221b96ed79668a5dcc47d87d9d95fe55ea7549e445b3b059f171f034 is not running
Error response from daemon: Cannot kill container: 6a8b257050be: Container 6a8b257050be551fbbe91211dfb209f8cfc1e4c160710a14fbac11af50a2c499 is not running
Error response from daemon: Cannot kill container: 7b1201ade092: Container 7b1201ade092e1c9efbf6139b5de5ebd5ab8b2954d653358580a61952458edc5 is not running
Error response from daemon: Cannot kill container: 8303665f3aad: Container 8303665f3aadcc3903b054e400c6756c0f84d9146f551ec5ddb2ce52433e830e is not running
Error response from daemon: Cannot kill container: 7efef7e91bf9: Container 7efef7e91bf98df6889836d0626cb4ba62222a8eedd905f3f96dcdef8375b251 is not running
Error response from daemon: Cannot kill container: efaea3c94d62: Container efaea3c94d62e9f92f3e56b5d4b0e250cf690952a65819fac30447aafba0f14d is not running
Error response from daemon: Cannot kill container: a70890d9eedf: Container a70890d9eedfd4e67325bf8eb917841cc3d1b72201231fad1b23ff64a9d3aba5 is not running
Error response from daemon: Cannot kill container: 9031b2d1c0cf: Container 9031b2d1c0cf5ad9a46c7759628c9f8b735705f7040a8dea9dff828d0aae59ce is not running
Error response from daemon: Cannot kill container: 628f9b3f2725: Container 628f9b3f272538680e773f0bc88edab394f6b5007bbcf98c39559f6421bd09f5 is not running
Error response from daemon: Cannot kill container: 2bb0930ebd2e: Container 2bb0930ebd2ed6c2a4df142a248f2615fddabb211bc8d14680afbee29be0dbea is not running
Error response from daemon: Cannot kill container: ceabf3ec914c: Container ceabf3ec914c281b54a8f55a9abeb0926689818eac8896f88e896c5afd21bede is not running
Error response from daemon: Cannot kill container: 2e9ffa55b022: Container 2e9ffa55b0226138b2da42abdc5b329679d76b72d95e68487de0c7fef3c0adcd is not running
Error response from daemon: Cannot kill container: 918946ba7a3d: Container 918946ba7a3df921493be91a4caacd452e4c3d83ac518e5f22120e836f5f8ed8 is not running
Error response from daemon: Cannot kill container: d5ff3436305d: Container d5ff3436305d76b4fbd71cff8ae6570cc8cb68703269d344dab78ecc4ae23b8d is not running