GUI acceptance tests using environment deployed from packages.

Build: #2128 failed

Job: Oneprovider archives incremental and nested was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
15 minutes
Revision
ac926e605a6b5528819b657cbc204091f50a9df5
Total tests
8
Successful since
#2108 ()

Tests

  • 8 tests in total
  • 14 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: 19c536718a85: Container 19c536718a85b8ffbcd51194f2ca3809bd156dd36f4057e290020e4e6878aabb 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-COAIN/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/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-COAIN/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-COAIN/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-COAIN/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
W0502 08:29:57.633030     434 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  48468      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: 994ddcaac982: Container 994ddcaac982116ed93abcf8d220fa4410da1e12223621e82c38296ff42f0975 is not running
Error response from daemon: Cannot kill container: 92bbd8351ca3: Container 92bbd8351ca3f039121511f8c6b4b18553926c79235fa607758fa6711dc3b518 is not running
Error response from daemon: Cannot kill container: 283d7de2f3ad: Container 283d7de2f3ad92c49eb2e55fab54bc5f553f8270b1afdf53dd6d13bfd82d7b94 is not running
Error response from daemon: Cannot kill container: c13ebbc7174c: Container c13ebbc7174c45d77ec3fd907cc544f8577b512c729810969441579921965875 is not running
Error response from daemon: Cannot kill container: 10a01aabbb17: Container 10a01aabbb17f03f0e9b4dd15d9e766d5580c1e4b12296ef1600f237e9c6a842 is not running
Error response from daemon: Cannot kill container: fd7f33d580f6: Container fd7f33d580f62635f0b4fed680c64466a2de1549ce47ab998faf8080e50af909 is not running
Error response from daemon: Cannot kill container: 83ab86fec6e0: Container 83ab86fec6e0cb3606ae4b9e96d81abbb55cc67f31d60b52fc9bce98364c3929 is not running
Error response from daemon: Cannot kill container: a8eb79029c56: Container a8eb79029c56d880cfc910dfbb2fd0538fa31dac07dfdee797bd383048ceae10 is not running
Error response from daemon: Cannot kill container: f4bdf09b51b9: Container f4bdf09b51b96e929dc8fddfc390cf2a440142c91803657a9d69c08a5df65e03 is not running
Error response from daemon: Cannot kill container: 0f3a9c3fa1e0: Container 0f3a9c3fa1e05aa3cdac92cfac1012c8cfc9b069ad5740d5cd8ba69d00667b05 is not running
Error response from daemon: Cannot kill container: 468b75660f17: Container 468b75660f177a7f2ca582adc03aa56e3fa4e3ca34a318f11f0234be319a8cd0 is not running
Error response from daemon: Cannot kill container: 3836050ebc11: Container 3836050ebc11a7d84076d47302f77f5164bb43f16fc2e6cd18d6e6ee73d31008 is not running
Error response from daemon: Cannot kill container: 1609c784385a: Container 1609c784385ac5fe7ce58249daca4a04ae481c7ef6baa183f466a470eb463c0f is not running
Error response from daemon: Cannot kill container: cc045bb190cb: Container cc045bb190cbb2cec0d8f096e3231e0b6e8c7029b2e2dba622b2bd0f6aa35391 is not running
Error response from daemon: Cannot kill container: 8f66d9cab7e4: Container 8f66d9cab7e45e64143af15f917b31a5bb19e4c74114018cef3a994c005ce3c9 is not running
Error response from daemon: Cannot kill container: bc4ff575b252: Container bc4ff575b2524bafec9f4641e1daefda244fa09a69d6fe2313faa780d6e763e3 is not running