GUI acceptance tests using environment deployed from packages.

Build: #2000 was successful

Job: Multiprovider basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
22 minutes
Revision
3472d8727468cf978131865efabe3f31a6595f39
Total tests
8
Successful since
#1990 ()

Tests

  • 8 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
  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: 71392609d494: Container 71392609d49408bdcecf0e108c42fea413ea22edeaa0b3542c551cc909f1c29b 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  46069      0 --:--:-- --:--:-- --:--:-- 46069
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 0557041bf1a2: Container 0557041bf1a232b45edf135b679dd0957205b4b0516315f5ae04c9037a82178b is not running
Error response from daemon: Cannot kill container: ece1fa5eebd8: Container ece1fa5eebd8aa0b81daa701bf522c1861d0db6c2b5007c7840c1fe44caef10b is not running
Error response from daemon: Cannot kill container: f96a9c646f49: Container f96a9c646f49b5c4f2ccdc6288cc409aebc9823614dd152bae9aa7a6fc05a145 is not running
Error response from daemon: Cannot kill container: 3f13c83f73f5: Container 3f13c83f73f5800bb3e3bd9dd41c676a3fd0b059e86567cd45532114c5fef274 is not running
Error response from daemon: Cannot kill container: b664e0f552a6: Container b664e0f552a679b03c11c17fe6f87b64aa34d09102e0c3aca81910a7b1270a70 is not running
Error response from daemon: Cannot kill container: 607b9a3508f6: Container 607b9a3508f65162aa3436b0b720b8c76b66ce9ce1d5d40f6c179cb60c672394 is not running
Error response from daemon: Cannot kill container: 74993783ee7a: Container 74993783ee7a32b0f72139fea9187e433dda5ded90efbad32954ec542d404dde is not running
Error response from daemon: Cannot kill container: 2f72b1ddfd08: Container 2f72b1ddfd08a66e1e27d4c93098f222f13dfda792498f68663ddea7d6eb45e0 is not running
Error response from daemon: Cannot kill container: 3a6b852ec994: Container 3a6b852ec99440ce273247c8ee8f9a13f0cf40e0df8b8332d2c76bcc70a0fd79 is not running
Error response from daemon: Cannot kill container: 4c2008d3e9c3: Container 4c2008d3e9c3e7588e8c03e03b38dccde4275ad67cb975c54fe7b43e92c41d34 is not running
Error response from daemon: Cannot kill container: 6c7659f70d25: Container 6c7659f70d2539feeb5dd39d368390ef8575d3f57e8dcb4f8a3547a7cc598680 is not running
Error response from daemon: Cannot kill container: 17943e2d7400: Container 17943e2d7400765ab205a736ac962db890de9a5aab906c7fd08779ba345df340 is not running
Error response from daemon: Cannot kill container: b5dce0f44b29: Container b5dce0f44b2960b2703f131566d9449a01119ec034ff64c97e81ed21f2b7f5e8 is not running
Error response from daemon: Cannot kill container: 29281c084a4c: Container 29281c084a4c357c6849eaf87b12e717e176c14166a499f8011aa6046d2bc2db is not running
Error response from daemon: Cannot kill container: bb89e0da2d1d: Container bb89e0da2d1d5086c740a7923ec2afb1f02164e94d40ea5550c6721019e72a8b is not running
Error response from daemon: Cannot kill container: da58394c06f6: Container da58394c06f6f390ccc8b696273e81f45058a6fe638b24ffc64269b147cac21c is not running
Error response from daemon: Cannot kill container: d9d769bc0bd1: Container d9d769bc0bd1f4e3debba2160e0bd6575393a6a0201dee2434a16d1b4271a921 is not running
Error response from daemon: Cannot kill container: 4cdcc6adb2bb: Container 4cdcc6adb2bbb9ea31404031c746bb1ad4c19e7be356142ab2b25f47195fc28a is not running
Error response from daemon: Cannot kill container: 3a0797f4318d: Container 3a0797f4318d209d50b53490c267ebfd2bc74c7067f0e5f3f2d8ab7104d75380 is not running