GUI acceptance tests using environment deployed from packages.

Build: #2150 failed

Job: Oneprovider upload was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
19 minutes
Revision
55cdb7fe92fff892fdb8cf16f00c4ce6627a4c4a
Total tests
7
Successful since
#2112 ()

Tests

  • 7 tests in total
  • 18 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  40815      0 --:--:-- --:--:-- --:--:-- 40460
Error response from daemon: Cannot kill container: 00b07cf782d1: Container 00b07cf782d144fa03a75feb1177980164c8ff160bb9ff2816e01e906f0bc27c 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-COUT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COUT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COUT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COUT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COUT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COUT/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-COUT/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-COUT/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-COUT/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
W0526 20:36:45.252913     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: 2f54e0c70a6c: Container 2f54e0c70a6ceddce88b6cc8439ed25852a5291ed55f580a73a6652a9063d37a is not running
Error response from daemon: Cannot kill container: e47336d9d1e0: Container e47336d9d1e02b438cf1d069fea1e1b879dea5a2dafea176db2c2c9e8d01cf04 is not running
Error response from daemon: Cannot kill container: ec1cc4b3dfc5: Container ec1cc4b3dfc5bb66b27ed285ff4d1b4d31ac3335ddaa53ed5c30699c5a6c25c1 is not running
Error response from daemon: Cannot kill container: 3a498c2fe369: Container 3a498c2fe3692669a312bcd1d940bd4dae0a6407c577b370b4f9fc492836c5f4 is not running
Error response from daemon: Cannot kill container: c1be6fbfec5c: Container c1be6fbfec5cde9b207b4d2a756d2992f738f4127691c92e15aba763845aad0c is not running
Error response from daemon: Cannot kill container: 6a11148d5b75: Container 6a11148d5b75d849674840754e429609e442d9b5c3a18b432143b7bfc58cc12c is not running
Error response from daemon: Cannot kill container: 1eafdd06df29: Container 1eafdd06df29785af0ee26b3dfee3d59f5bf7cb5357158684391519f81a69b9f is not running
Error response from daemon: Cannot kill container: 6cf11c4eb14e: Container 6cf11c4eb14e1eb650852698117a6b212f1cd21ec2e7fe6139e606d02fe63b6e is not running
Error response from daemon: Cannot kill container: 3385ed1d11bf: Container 3385ed1d11bf51b17d52825f3ec3bb0b5b261a150e8c88f8412e15d7a8efa6f3 is not running
Error response from daemon: Cannot kill container: ceddb2415afd: Container ceddb2415afda10c0e0203979b348fa11cc9ef58184738ca4e36c758bbbe8c89 is not running
Error response from daemon: Cannot kill container: 03376c6042f4: Container 03376c6042f48508306ccb7081cf83a4318107be173f7784c09e6fa3e592357a is not running
Error response from daemon: Cannot kill container: f9c47351f39d: Container f9c47351f39d720aa4dab867aa2e3bb06d85de964a67900e04cd6683ce487336 is not running
Error response from daemon: Cannot kill container: 459da78c88c5: Container 459da78c88c5862988897c6a70f0cefc4d6baaf40cb804a31a65e0357eb1e129 is not running
Error response from daemon: Cannot kill container: cb1e5cd98bdb: Container cb1e5cd98bdb5ee70b28482b24e52d23dcc7a0b6494f6121b08aa1688f55c872 is not running
Error response from daemon: Cannot kill container: 030ed6748959: Container 030ed6748959dd29a5d01da4743fba9ba9e86fe5aec3cf5551bee16216edfb5c is not running
Error response from daemon: Cannot kill container: d20fb2010e9a: Container d20fb2010e9a70270495a7d1f936c625cf6cc3f970916f4392c899fb6ed435d3 is not running