GUI acceptance tests using environment deployed from packages.

Build: #2163 was successful

Job: Transfers directories was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
22 minutes
Revision
2a6ac951983b0da397726653daa1ebcdbbe74ca8
Total tests
5
Successful since
#1990 ()

Tests

  • 5 tests in total
  • 21 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  34466      0 --:--:-- --:--:-- --:--:-- 34466
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: 812bdbb1dc97: Container 812bdbb1dc9732fe0c9a6203c845b280fea8c2fa622f051aa4d9b2c726cefe91 is not running
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
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-CTD/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/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-CTD/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-CTD/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-CTD/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
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable
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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  44314      0 --:--:-- --:--:-- --:--:-- 43896
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: c69869f74012: Container c69869f740129ff615a6c9b0ee89711d4ec1c0720e651205f965d9c2a34679d1 is not running
Error response from daemon: Cannot kill container: 7fddf612ed3f: Container 7fddf612ed3f97715d54a934a008a5e9acda28ef0b9c475b9361f6eedb41914c is not running
Error response from daemon: Cannot kill container: ef2c0f84a1c7: Container ef2c0f84a1c764f0108fd263e1ad0e710959f6daa0480a376721f7e15556d9cb is not running
Error response from daemon: Cannot kill container: 0971d3cf88da: Container 0971d3cf88daa77482253621466a55c1cd129024e97c4629f9067ecc8d59f753 is not running
Error response from daemon: Cannot kill container: c201461a9aaf: Container c201461a9aaf48cc94c2a2fd4a40b4ca07bc2ce30cd3d20b5a3768b1bc65e3d0 is not running
Error response from daemon: Cannot kill container: a3f4814c5ef2: Container a3f4814c5ef29515c13ebc404633f552b9685267432948f3b2f5687954038520 is not running
Error response from daemon: Cannot kill container: e6faa058629a: Container e6faa058629a6d8bd73ac6cd84d7d4601292d93841a8bea10f5d8f74470b53eb is not running
Error response from daemon: Cannot kill container: 850422d0b01b: Container 850422d0b01b740ea78ab8b116b2c0704db7a8b558ad161e20df6edaa95acba7 is not running
Error response from daemon: Cannot kill container: fc016e71a0c8: Container fc016e71a0c8f5ce76aeadc799644586d9e8d70b406a8e000643c5e68138d2eb is not running
Error response from daemon: Cannot kill container: 2ddb45f23846: Container 2ddb45f23846729c2108f15087706a775d0439a089da6228e2ae0e523c8de198 is not running
Error response from daemon: Cannot kill container: c8a5ba130262: Container c8a5ba130262dd370943621a7cdc2feb185255c21db89855c77c9628f74b622a is not running
Error response from daemon: Cannot kill container: c8a364bf7610: Container c8a364bf761067572a7130faff2fb42372594fd6e506216ed7491f4f67b14dea is not running
Error response from daemon: Cannot kill container: 05625046c55b: Container 05625046c55b6086fbdfe3e1f6d53031e9245abfc7ae4cb57ec8e148ec0f6264 is not running
Error response from daemon: Cannot kill container: c607bdae8f33: Container c607bdae8f33debe6a9aee5014ee76fdaa57d2961506d3f636bf952c2119810b is not running
Error response from daemon: Cannot kill container: 0ba0dff56333: Container 0ba0dff56333501977994f5ba8a1f8078ba83cd3faa6599d668638c0a83aea8a is not running
Error response from daemon: Cannot kill container: d23033fc1b91: Container d23033fc1b91ab73100dc527b94b742cee6cb682cd31f640fdd7859469c3f95e is not running
Error response from daemon: Cannot kill container: dea8c019892f: Container dea8c019892f041867523ed1e0691be9bd9b111af502b879bb6304289c900a55 is not running
Error response from daemon: Cannot kill container: 86c015c436bf: Container 86c015c436bfefdf0bc296aeca4a21d8ee387a9b18563366c706092deddde920 is not running
Error response from daemon: Cannot kill container: 2962d9786a9c: Container 2962d9786a9c0d63ae115c48ffc3960fd92a75191048cc6e55d7187843388f48 is not running