GUI acceptance tests using environment deployed from packages.

Build: #2041 failed

Job: Multiprovider basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
21 minutes
Revision
ede44e43ac4719043bc240bfa18cbbd42526087c
Total tests
8
Successful since
#1990 ()

Tests

  • 8 tests in total
  • 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
100  4653  100  4653    0     0  44314      0 --:--:-- --:--:-- --:--:-- 44314
Error response from daemon: Cannot kill container: d6dd84605bb5: Container d6dd84605bb56cc42b5663e839db0911d9b9bb720b9d47e9a72d8b534d957594 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-CMBT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/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-CMBT/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-CMBT/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-CMBT/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  45174      0 --:--:-- --:--:-- --:--:-- 45617
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: e3e1903cd62f: Container e3e1903cd62f587ddbaba025cc0a42b288c0d50ef3dbf4590a07ec69cdaa8d22 is not running
Error response from daemon: Cannot kill container: e670803e574d: Container e670803e574d129e070415f5bc2ef6afaa1bd1afa9e10234589193cefbc35cf5 is not running
Error response from daemon: Cannot kill container: 7aaec3fbdbe2: Container 7aaec3fbdbe2b6fde2021df0ee175679b02c5bd468775be623fe1f36f781b54c is not running
Error response from daemon: Cannot kill container: 7bcb3ae939c1: Container 7bcb3ae939c139a0247173ca891e202e5f972ddf7115d99746a49d71d39b7dc9 is not running
Error response from daemon: Cannot kill container: 689d853cca11: Container 689d853cca11d425ed1edf3ac6c8023f0108a0bfc9768cfbf32c03059e003dca is not running
Error response from daemon: Cannot kill container: 1a2a4e769b3a: Container 1a2a4e769b3a350ca3389f0a35b569643ec10a3e0ae05440987cb1ec131dbb94 is not running
Error response from daemon: Cannot kill container: d85dde8d2a12: Container d85dde8d2a126909175d57917c0b80ff9b06d83c7fe804390ff329c029ffff15 is not running
Error response from daemon: Cannot kill container: b7abfa894d0c: Container b7abfa894d0c425eaad7f98001c5ab94411a1b51cf05c236c84cc2dc707789e7 is not running
Error response from daemon: Cannot kill container: 9f04a4afc80d: Container 9f04a4afc80d963a1d3e67cf8e0e680405c586d47f96706f785a83b408dde31f is not running
Error response from daemon: Cannot kill container: f574f27dea86: Container f574f27dea867684ce821076f42a3a21d5aade21f3bd50f2431341fd5377406c is not running
Error response from daemon: Cannot kill container: b16b1e5bf2e8: Container b16b1e5bf2e84edc26429ced8ebbb8b21df22d97d809e462eba4498aa0fdcf89 is not running
Error response from daemon: Cannot kill container: f2cc2cbb6f5e: Container f2cc2cbb6f5e86bffeee702bdf3e35caeaaaddc9de103924977d36bcc078487f is not running
Error response from daemon: Cannot kill container: c5e7bb00605a: Container c5e7bb00605a9b295e511c19e76f0d0cc94adee9d81af4b875a386ab7bc47af8 is not running
Error response from daemon: Cannot kill container: 6c6d2db32599: Container 6c6d2db32599b6ff054cbc70dd8a25ad27f79783f185ed47511005ca99b148e5 is not running
Error response from daemon: Cannot kill container: d930bd699537: Container d930bd69953715ec635e16a9b89acb994047421a50610006dffc4ff8d1c48455 is not running
Error response from daemon: Cannot kill container: acb980aa07a5: Container acb980aa07a55b8886194ece09935f4b9bffba96d7b041a4d6cf4eee35188de8 is not running
Error response from daemon: Cannot kill container: a5aa9379da00: Container a5aa9379da0083fe8413e89252539ada42d6b6ef7955667705da47b070239548 is not running
Error response from daemon: Cannot kill container: b83e8abdbb27: Container b83e8abdbb27b822b33a579c614bff604b01fbff6de483eebb0d649be55dc126 is not running
Error response from daemon: Cannot kill container: d99a0b0b047c: Container d99a0b0b047c7c084ba4aa888d3c5649053bd78cb9a5bc931f4d21757b09d39a is not running