GUI acceptance tests using environment deployed from packages.

Build: #2135 was successful

Job: Storage sync charts was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
7 minutes
Revision
72d4158537fcbe5e765cfeaf323ebd441ede24a2
Total tests
1
Successful since
#2113 ()

Tests

  • 1 test in total
  • 5 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  47000      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: 0227a9430801: Container 0227a9430801025af6db7f190184188d96bd748200a2f344c3b77c8ea189a86e 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-CSSC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSSC/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-CSSC/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-CSSC/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-CSSC/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
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]
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
W0509 10:54:28.958508     439 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
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  42688      0 --:--:-- --:--:-- --:--:-- 42688
Error response from daemon: Cannot kill container: 4d58759beb60: Container 4d58759beb6018f7da466b930fe9d099f69c59feeabe8ed851cd2dfd1bfe8fb3 is not running
Error response from daemon: Cannot kill container: be1e550f837e: Container be1e550f837e7d048aa6eb5601d58b0e13b7d8461cbe3598b4bb689c0bd21559 is not running
Error response from daemon: Cannot kill container: c193be926e5b: Container c193be926e5bfd85f3725ebb773480afaf03ef007f4bfcb5bc734f99c2f8c243 is not running
Error response from daemon: Cannot kill container: d2232dcd2b0a: Container d2232dcd2b0a611c7d027954470935356b2836c3bbede4c7b8427dfbfeff2e7d is not running
Error response from daemon: Cannot kill container: c8dabb326d20: Container c8dabb326d20c1eca858c612a2d405fcda850d0ea604ffbb9d3a42859c92ed24 is not running
Error response from daemon: Cannot kill container: 33fa522e9260: Container 33fa522e9260f2dda769551e6c3b92d522d8c24ea142e5dc0a4a798937857f30 is not running
Error response from daemon: Cannot kill container: 44c489a44817: Container 44c489a448172b9bd447736f4d377d2516c53736cf294fdec495cbea2db530c2 is not running
Error response from daemon: Cannot kill container: 817eae35b77f: Container 817eae35b77f866091d558f7948dfd76dfa7b4a2f7483cafa29223fe68ff98b3 is not running
Error response from daemon: Cannot kill container: c46ffef9351a: Container c46ffef9351a1b7fa7621025516dcb3fb824751165f43325687178fac2f0da7e is not running
Error response from daemon: Cannot kill container: 7ce788507b0b: Container 7ce788507b0be0a2d67db80c4f6f6ebc2321ab4f430031e206a2278f84174f58 is not running
Error response from daemon: Cannot kill container: 9e9cebf657c5: Container 9e9cebf657c538b19f90bff560659fc99d5b8f262d8ac45e15fdccfedb51b1da is not running
Error response from daemon: Cannot kill container: 18dd11d71e58: Container 18dd11d71e58c4e005df5792ed2be288b221a75132b248401c862d8893e21863 is not running
Error response from daemon: Cannot kill container: dd8b9525cf7e: Container dd8b9525cf7e7dc397c19cc9fe495957569ca4c18a32ad33b161b27ade63f0c0 is not running
Error response from daemon: Cannot kill container: ab0bad2abf39: Container ab0bad2abf3902a83bf722055eb18db55baef0d1cfce0df28ddf156628a43068 is not running
Error response from daemon: Cannot kill container: 0d03de4abd90: Container 0d03de4abd904fab7c35b7d301cf89c4542c9af2d868ab33f70b1c57768c9ae4 is not running
Error response from daemon: Cannot kill container: 9f85dca54c8a: Container 9f85dca54c8acdb4d56095e101c89bf525485cb141e8440ef0fd676b9030239f is not running