GUI acceptance tests using environment deployed from packages.

Build: #2165 was successful

Job: Multiprovider QoS was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
10 minutes
Revision
2a6ac951983b0da397726653daa1ebcdbbe74ca8
Total tests
3
Successful since
#2082 ()

Tests

  • 3 tests in total
  • 8 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  47479      0 --:--:-- --:--:-- --:--:-- 47479
Error response from daemon: Cannot kill container: 593ebaaf73d2: Container 593ebaaf73d25e04a418441ed75fac76c45e9a76c604cd9e8111f596b4626297 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-CMQT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQT/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-CMQT/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-CMQT/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-CMQT/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  46530      0 --:--:-- --:--:-- --:--:-- 46530
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 20faa1dbd33d: Container 20faa1dbd33dbf60927b2e962d4f34e5fafb8c055e0bd2e5827484c768deb057 is not running
Error response from daemon: Cannot kill container: 59291b3b7e63: Container 59291b3b7e6337aa547c9d66a112958b7e85757b8a82151a292b57e07b307d80 is not running
Error response from daemon: Cannot kill container: 87baf5e66481: Container 87baf5e66481e5412e1d5f72be4610b4bdebde7789647af13ad8176289829022 is not running
Error response from daemon: Cannot kill container: 92bda86f7f95: Container 92bda86f7f95df8a55bcf0cef1bd6a64b034c080d52fc6b2708df9c1213cf55f is not running
Error response from daemon: Cannot kill container: 5f99c3ae3944: Container 5f99c3ae39440eca2a3e66d746dcc45d9ba2ff96c83a2db1f046bc0c58a7b95f is not running
Error response from daemon: Cannot kill container: 4661f27906a0: Container 4661f27906a06196855782f60060b05909e8c635e2ed93967b7135b16e0d6293 is not running
Error response from daemon: Cannot kill container: 21dacec296b5: Container 21dacec296b57ecf821a8dc50b35e60bf73dc15a3976d861f95d303a3514e1bd is not running
Error response from daemon: Cannot kill container: 6f84a0a33394: Container 6f84a0a333940d7f2d1e435b0edc27434cafd386e5ad00e24390edd1ae8e3972 is not running
Error response from daemon: Cannot kill container: e69d795f8a97: Container e69d795f8a973a7133375fdb33d27001765c35d1e027e03de3bff873537bb69d is not running
Error response from daemon: Cannot kill container: 1b3e7204f4a1: Container 1b3e7204f4a10ae2f1329d0b9bbae01d9af3ca5b7edc1c958d8312fe93061cc8 is not running
Error response from daemon: Cannot kill container: 64048e3d1f39: Container 64048e3d1f39a7e931aec71247177272862de1d76dd9306b55f7754b68c29269 is not running
Error response from daemon: Cannot kill container: 4ed19c9d7633: Container 4ed19c9d7633443c4990d9558a6f8c9265a501f49259a07891dd56e276291b56 is not running
Error response from daemon: Cannot kill container: 61c302735463: Container 61c302735463b85fac410663d963fcc9b6ab1db505c1bf757df420aacc91d06b is not running
Error response from daemon: Cannot kill container: 533bf03a40ac: Container 533bf03a40ac7f19e0f2ae80efe2e5a4013ca79dc206248abc2e82ddb429c9f8 is not running
Error response from daemon: Cannot kill container: a95399e766d2: Container a95399e766d21bde69d96ec9dda584ec8ab1d7e5b81cc4ee86b5a49b09924996 is not running
Error response from daemon: Cannot kill container: 62acf428dbb1: Container 62acf428dbb196850a63139a5e37eb9eabbbffd66cb8ad792d773b1ee24c329b is not running
Error response from daemon: Cannot kill container: 3f939a1680ee: Container 3f939a1680eed3f5c13e8c231dad08c0e6219c7f7ae5540b2c1af33e26a7de53 is not running
Error response from daemon: Cannot kill container: d74c645acc0a: Container d74c645acc0a3f2954160c8987c5c8cd90354255975344687067100581f7277d is not running
Error response from daemon: Cannot kill container: 2d7bfc6713fb: Container 2d7bfc6713fb483b591319f39fcfd653a92c3eab01547e14d2c6755af336377d is not running