GUI acceptance tests using environment deployed from packages.

Build: #2027 failed

Job: Chrome onezone automations tests was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
29 minutes
Revision
06b7ddbe39e2302126bded895dfde2e9f3fa8004
Total tests
29
Successful since
#1998 ()

Configuration changes

Job Chrome onezone automations tests with key ODSRV-GAPT-COZATT no longer exists.

Tests

  • 29 tests in total
  • 28 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  35792      0 --:--:-- --:--:-- --:--:-- 35792
Error response from daemon: Cannot kill container: 431c14420705: Container 431c14420705de3bc1562be2f09a0eb0bac38c674150e5e5eb0730063985e111 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-COZATT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/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-COZATT/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-COZATT/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-COZATT/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]
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
W0317 08:26:44.681499     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  38454      0 --:--:-- --:--:-- --:--:-- 38454
Error response from daemon: Cannot kill container: 3ec89b11111d: Container 3ec89b11111d7180e2a386b29a9c148499718ebf0888de8863be8abda42d84da is not running
Error response from daemon: Cannot kill container: 22cfa801a579: Container 22cfa801a5791d38faf01984bd28273242daea87db99ae6cb9865e94378359a5 is not running
Error response from daemon: Cannot kill container: 926f53d14c6c: Container 926f53d14c6c9f83973a4695a529eeb4218f136c96f8a554b99a0387b1e9dbed is not running
Error response from daemon: Cannot kill container: da3954298520: Container da395429852057322b407cd7e50c21f8375eec9049f47b0b4663ebcfe234a059 is not running
Error response from daemon: Cannot kill container: 7d0d14e91d83: Container 7d0d14e91d834fe3af68ea3c2eb73548097a6488f14c71b66ed519ad16b8702a is not running
Error response from daemon: Cannot kill container: 0dad976110b3: Container 0dad976110b36b1c6d260f89b9c6c014874e6991a2ff43865f114f6d5cd39660 is not running
Error response from daemon: Cannot kill container: 17fcf6915245: Container 17fcf69152452c02aa45e1b23cbeb105a2c6c8262384df0fdee7a7c2e5862ca7 is not running
Error response from daemon: Cannot kill container: d7e06aee28cf: Container d7e06aee28cf42d1cfbdd95378d7ec0ba63a44ae14b27c6c73613f6f90adb2c5 is not running
Error response from daemon: Cannot kill container: 1554da26c001: Container 1554da26c001d8578b976d85a57d07b65988f74f6d8fdec5b6b5e3628eba7871 is not running
Error response from daemon: Cannot kill container: f5f95f364fa1: Container f5f95f364fa1f89849145214e16be52d1696026eeff753bb954564b87b7e9d01 is not running
Error response from daemon: Cannot kill container: 9c809fcdf9de: Container 9c809fcdf9deb8f8d33c9cb355b2166999b523e349ba9b9082b4059a0ac32c06 is not running
Error response from daemon: Cannot kill container: 1190e5b0b63b: Container 1190e5b0b63b40a22dc91b9691427fe9dd3c736616d3c8978a8f0b08ee512759 is not running
Error response from daemon: Cannot kill container: 8dae3a6e046a: Container 8dae3a6e046a56ee38cc59d6d8cfe5749a246654d693c6981f1469d6929d0f00 is not running
Error response from daemon: Cannot kill container: ed4f4b0b6b28: Container ed4f4b0b6b28adb7909660a025ea1f644627abecf60ac8d6071afe494c2825c0 is not running
Error response from daemon: Cannot kill container: 35377631297a: Container 35377631297a9c9890e3a78f104b132c5157534fc15ec453380342888bc62de8 is not running
Error response from daemon: Cannot kill container: efbcd62d0911: Container efbcd62d09118071ba1f6c9cc4bbf51378569a840e87e8f6ac8511e2098395ee is not running