GUI acceptance tests using environment deployed from packages.

Build: #2121 was successful

Job: Multiprovider QoS storage was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
18 minutes
Revision
531283e2b89b3833269b775ff1b3609165404e1a
Total tests
5
Successful since
#1990 ()

Tests

  • 5 tests in total
  • 17 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  46530      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: ceba6760ce9d: Container ceba6760ce9dc1fabe88a0b9d4214e2878ad3c9aabceafba8a72bdb910926efd 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-CMQS/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQS/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQS/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQS/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQS/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMQS/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-CMQS/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-CMQS/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-CMQS/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]
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]
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  37224      0 --:--:-- --:--:-- --:--:-- 37524
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 8c03a015d14e: Container 8c03a015d14ec38d0187e32deee34f99617d37a5e77287e97bd346c8fb9319e3 is not running
Error response from daemon: Cannot kill container: f6a4d03e21f5: Container f6a4d03e21f587dbb4cae22a2c3b1181efb87b7f3a6311b63d17062f3007bb24 is not running
Error response from daemon: Cannot kill container: e946d6178eea: Container e946d6178eea5cf0fa1a1d7799dfd3802841e84a521915f558b9138a0157cab6 is not running
Error response from daemon: Cannot kill container: 80d28717ec5b: Container 80d28717ec5bb8a3a5b93bfcef8bb4dcc617804ad5fedf5c1a880a40ccde8e55 is not running
Error response from daemon: Cannot kill container: a782fa842ca1: Container a782fa842ca18344f60ffabdab43b0054a952bd1663db147b17a10f4aa880b54 is not running
Error response from daemon: Cannot kill container: fcb01b0fbadf: Container fcb01b0fbadf1627638f4084747a6b47aaf21077b3fa7f947b0ca572775a5d83 is not running
Error response from daemon: Cannot kill container: c6bc244ba062: Container c6bc244ba0628dccf1038fd180133ce80cf59e6d36752463fd2c7ff23e43ca3b is not running
Error response from daemon: Cannot kill container: 5b2787522504: Container 5b2787522504d26f3d92cbd12a052d53ab846699a2faa2010f0ce763af6af330 is not running
Error response from daemon: Cannot kill container: b88ba6df64e2: Container b88ba6df64e2456e8d3556dd3e09c1ba96088d37f89924a941caf65bd4d0df92 is not running
Error response from daemon: Cannot kill container: 825b4388e501: Container 825b4388e50149f4883e03af6ca409654cdcbe52d586ddb5efb2121af81d61f6 is not running
Error response from daemon: Cannot kill container: c7f86ac9daf7: Container c7f86ac9daf7a0a4b29d952f3f830ee0fcf5123791e33d71c0dc736850091f0a is not running
Error response from daemon: Cannot kill container: 2060e78a6336: Container 2060e78a6336870e470de35900dad8a2c1dab98b606cf1753e465b36a7e789d5 is not running
Error response from daemon: Cannot kill container: 8628cc0f5cf0: Container 8628cc0f5cf02c6861a1c32bbce91fdaea3d60d1a53d286083f1d32e9478a194 is not running
Error response from daemon: Cannot kill container: b4b3bcc1a842: Container b4b3bcc1a84216d58964c0ae934482432b89eaea9180b72cc9bbb8b9df30c593 is not running
Error response from daemon: Cannot kill container: d51b790859e0: Container d51b790859e0ce7826aeb6bb0e8ed3e30f3fab476c065b91966641622f95c9b3 is not running
Error response from daemon: Cannot kill container: e082ed9fcc41: Container e082ed9fcc418399501896e922bd67d2eb1ab37afb93b600ec60c3c602b529e3 is not running
Error response from daemon: Cannot kill container: 03226d47d6eb: Container 03226d47d6eb0822c3460eec47e825197ab629e1590a5f2422d895c7eb825983 is not running
Error response from daemon: Cannot kill container: 036ea17cffa3: Container 036ea17cffa3cb314f797ffbfa287585641a0100907497e35e13ee46c23acd1f is not running
Error response from daemon: Cannot kill container: 51d2bfe3e9f9: Container 51d2bfe3e9f95ba5d335951b38733f90d795e6247cd49e0aada6837a4af352d9 is not running