GUI acceptance tests using environment deployed from packages.

Build: #2273 failed

Job: Onezone tokens delete was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
32 minutes
Revision
624ddd1dfa241fb01c10e610d5a920a26351648e
Total tests
10
Successful since
#2197 ()

Tests

  • 10 tests in total
  • 31 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  42688      0 --:--:-- --:--:-- --:--:-- 42688
Error response from daemon: Cannot kill container: 1bbbed916847: Container 1bbbed9168472c991111f5c429965e0486f57696fdd2266a7633c9c65cbf62c4 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-COTD/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/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-COTD/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-COTD/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-COTD/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
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
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
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
W0824 20:32:08.085687     505 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  32312      0 --:--:-- --:--:-- --:--:-- 35250
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 45c29e05f186: Container 45c29e05f186d22be4dd6beb07f29b1ed69f37112b8bc88495aa1f3b0d9505d1 is not running
Error response from daemon: Cannot kill container: 0d4fae37e1fc: Container 0d4fae37e1fc398f7c8423c7c013aeff07c4f48371f0e3afbe409e613f78e962 is not running
Error response from daemon: Cannot kill container: 51ccb9805acb: Container 51ccb9805acb3c1709541c718f1c1034854b9cdd23d7928204663c39e39fecd0 is not running
Error response from daemon: Cannot kill container: 5b56753f4770: Container 5b56753f4770f65c181cdda97295fdcceece113e5494f0c8e29eab7137753058 is not running
Error response from daemon: Cannot kill container: 224feef7a7cd: Container 224feef7a7cda2533e5e4b49589a5d38e32b8e35e0f444f4e81d16e499cbbe9c is not running
Error response from daemon: Cannot kill container: 38540e4505a7: Container 38540e4505a7f0a8d21a21f1b01b7b1f73fad18ee4df632208587e7d6b72e20e is not running
Error response from daemon: Cannot kill container: 0bbad7d32ce1: Container 0bbad7d32ce1302345cf3bfdc3dde360811dacbd293a0d07f927afa77453a32c is not running
Error response from daemon: Cannot kill container: 23e38a708eea: Container 23e38a708eea665cc3610fe92927b5b46f3d5f7ef8dfa1937fc2a77232a1b94a is not running
Error response from daemon: Cannot kill container: 999d48aab71d: Container 999d48aab71d851bff5431e8e6a3f0285eaea8b1ff76d78260cc59b9658eeee7 is not running
Error response from daemon: Cannot kill container: 80b7bcfab47d: Container 80b7bcfab47d5a0135a1d5f250408fa12e9bb1e16e2bcdf41a79f59c318f881c is not running
Error response from daemon: Cannot kill container: 799c3f32f672: Container 799c3f32f672b9bf7fc7b6dfcba24e60b8b703eb1537187635fbf75400480a20 is not running
Error response from daemon: Cannot kill container: 4e8a2c0d4a93: Container 4e8a2c0d4a9341afd3793527a6b9d18ee4e6a328308c61bf478bd7da5177cdd9 is not running
Error response from daemon: Cannot kill container: f404d4ed8add: Container f404d4ed8add5412ed1f6944e736e0112143ec102644f50ad8b08204c943111e is not running
Error response from daemon: Cannot kill container: a39a8945e05f: Container a39a8945e05f15a34f8cbabc3a4585a1c408940da5632e1cc093bf3874088536 is not running
Error response from daemon: Cannot kill container: 771cddf5cfb5: Container 771cddf5cfb568eea03bea0072c67d1044339075cc7123719523e6d3bdae9180 is not running
Error response from daemon: Cannot kill container: 86f6f0f7cc41: Container 86f6f0f7cc414a55bd270d0eddee2665f94705d395a1cbd922ecd217746b8caf is not running
Error response from daemon: Cannot kill container: b721891799f8: Container b721891799f84a8d355fcbf82649733249768a1442bb88ea613ffdc45b3bc2d7 is not running
Error response from daemon: Cannot kill container: ee59acabb0ae: Container ee59acabb0aedecf595815abeb336f8907dc7519e98c268154f6184190f64de7 is not running
Error response from daemon: Cannot kill container: 08ac7ab6f9e9: Container 08ac7ab6f9e9b766f7fd13f25b2aaf790cb695905146b07e8019a0f1b81e0ccc is not running
Error response from daemon: Cannot kill container: 47309b0f39e5: Container 47309b0f39e5d280d94d69d3b61281dd8bf8f2154f76497d2967f8c4e26e2575 is not running