GUI acceptance tests using environment deployed from packages.

Build: #2107 failed

Job: Oneprovider ACL files metadata was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
25 minutes
Revision
616ef003a0a36dc00e59f722ca7550385601e480
Total tests
10
Successful since
#2082 ()

Tests

  • 10 tests in total
  • 24 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  39769      0 --:--:-- --:--:-- --:--:-- 39432
Error response from daemon: Cannot kill container: 87bafd3446ae: Container 87bafd3446ae043c5878e8844b76d57de39bdcc19fe2820a7f225f2c42b6f8e7 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-COAFM2/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAFM2/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAFM2/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAFM2/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAFM2/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAFM2/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-COAFM2/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-COAFM2/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-COAFM2/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]
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
W0419 09:01:44.636208     437 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  40815      0 --:--:-- --:--:-- --:--:-- 40815
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 5bf820e807fb: Container 5bf820e807fb5463587c8d7be94526fe0729d425d58ee5fd48f0e354c282f87e is not running
Error response from daemon: Cannot kill container: a913c76bffa9: Container a913c76bffa9f398283664eca26a07c78e8bbaf98daed9872b583b7e4b1edd93 is not running
Error response from daemon: Cannot kill container: a18f4c02f502: Container a18f4c02f502a09a4cd6da5beec67a992b82a7e9a5d45fba4d1045e6e8ab4966 is not running
Error response from daemon: Cannot kill container: a8239855ab15: Container a8239855ab159051e8106fe454904748c900af52b24d82d50a5678e981ad5a39 is not running
Error response from daemon: Cannot kill container: aa3abbfb8914: Container aa3abbfb8914c5f1568ad3d0b0d17b91dfc0d7f69e3884b7a67810db9c5ef045 is not running
Error response from daemon: Cannot kill container: 77d425f8d614: Container 77d425f8d614ec83e5494da9cc4479d4f27ad0ad41844dd702826b59c9f2135f is not running
Error response from daemon: Cannot kill container: 9d7bfcde71a9: Container 9d7bfcde71a974a1aae99bb7d849a0f5a3c340c061b65e5f985b7d0cc4d17b40 is not running
Error response from daemon: Cannot kill container: a06dabb64cbb: Container a06dabb64cbb923f3518bd9299eb3058a8079932ce15b7e556ec5dc860d2e836 is not running
Error response from daemon: Cannot kill container: e8d3bf6d36a0: Container e8d3bf6d36a0f14761947e78f9d9121fe8250808e5e9a747f7f1fdf9d932439f is not running
Error response from daemon: Cannot kill container: eb0120a20448: Container eb0120a204481382981308ee818c45bab6e40bda0069527b042e185def8b9c56 is not running
Error response from daemon: Cannot kill container: 4cea9176e4b5: Container 4cea9176e4b588326cb3d49dcc0820d8ececcf8c54338fdd4208ffc72fd045f7 is not running
Error response from daemon: Cannot kill container: 8fff69d47f28: Container 8fff69d47f2805a23283ac3373538d5297d36e0eb1519adfd10c68fb00e3c94d is not running
Error response from daemon: Cannot kill container: 9bfa9bfa2a5f: Container 9bfa9bfa2a5f1d5d54f14d486a51915cca876beea5bd404a81a83b50b6845c35 is not running
Error response from daemon: Cannot kill container: 1904394bb37e: Container 1904394bb37eeb08cfa5e89223ee2569182445fda04832df9f2c46c4697f04d4 is not running
Error response from daemon: Cannot kill container: 4570e06e541e: Container 4570e06e541ee0a33142d5dcfbc8fe8594b97738e37613a63331f111d0cbf5a8 is not running
Error response from daemon: Cannot kill container: 87139dba3b55: Container 87139dba3b55ce334bed67099ef32cf0791c4336ce5456abc05136dbd42c7540 is not running