GUI acceptance tests using environment deployed from packages.

Build: #2017 was successful

Job: Onezone invite tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
26 minutes
Revision
1c20564ae2aaf4956bec091653f5539a2459478e
Total tests
9
Successful since
#1969 ()

Tests

  • 9 tests in total
  • 1 test was quarantined / skipped
  • 25 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  46530      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: 598b3596ce52: Container 598b3596ce529b5e6c0f357dd2411752fc6ad8dfa0e298323881e2d5e9b64abf 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-COIT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/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-COIT/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-COIT/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-COIT/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
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
W0307 10:39:23.903970     494 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  46530      0 --:--:-- --:--:-- --:--:-- 46069
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: 2bef3279bf83: Container 2bef3279bf83969925e8223a9c2ea6f2a41e925933ca95b131c5f30af550bedd is not running
Error response from daemon: Cannot kill container: b368190174c1: Container b368190174c1a387617083d7a03b17b51d8cd84526bb0fe96dc21573e3d6f789 is not running
Error response from daemon: Cannot kill container: 71d7ae7f0ce7: Container 71d7ae7f0ce799829efb47d39ec64095e4f86292c7f89d203ded772f508b822d is not running
Error response from daemon: Cannot kill container: 539c90595a08: Container 539c90595a080d183bcb60c143f9fbab146030e8bb1493b88d6a84c2add024df is not running
Error response from daemon: Cannot kill container: ec458befb0bb: Container ec458befb0bb86aa5d47bc232065ab6f9d769577d1268777cf9d11166963909a is not running
Error response from daemon: Cannot kill container: 38d726b9fd2f: Container 38d726b9fd2fda9feb1b83b51c9e906ca70d4641a3421c8aeb81c89714d87cd6 is not running
Error response from daemon: Cannot kill container: afa644b7c2ba: Container afa644b7c2ba2584ef4e02d42468234872d3595afafe38d53630c85c32068148 is not running
Error response from daemon: Cannot kill container: dbf9273db5d0: Container dbf9273db5d05dcfd1b0afbd34ebe11cd286d02a7d953b634c8790a63a214437 is not running
Error response from daemon: Cannot kill container: 439873cb4da9: Container 439873cb4da9c820bc25c51659c8a5ac165fe1dbd1037c4cbc3cbc487526ab68 is not running
Error response from daemon: Cannot kill container: 5f393bcaa156: Container 5f393bcaa156b431224658c1e91a3c0320bbedfbf71ca009fcb27fe9519bcafb is not running
Error response from daemon: Cannot kill container: c8f307b84bc0: Container c8f307b84bc0634be0c6b37e2a59fe18558e4e50119f3acc32660ae6c7b7d993 is not running
Error response from daemon: Cannot kill container: 2731e338b139: Container 2731e338b1394a5ee37b5ee2946d23823cde3faa792dd28d69ef6f01a167d697 is not running
Error response from daemon: Cannot kill container: 721d58b58a76: Container 721d58b58a7698c2f73055cc3e62291a4d7728f99a145473c147a18e884c7fa8 is not running
Error response from daemon: Cannot kill container: 29212d43b2f2: Container 29212d43b2f2c16773ee768dec806037f42eb2e670f19bb050a605e158bba96c is not running
Error response from daemon: Cannot kill container: a5438dfae522: Container a5438dfae52254d174534fdc96565f0e6503c9bcf9277b9264c4fd842bbdda7e is not running
Error response from daemon: Cannot kill container: 490dc30546f3: Container 490dc30546f3def63c33d574ec4d9479b150d937c8309e17ec85367f8c4c180a is not running
Error response from daemon: Cannot kill container: df94f1148774: Container df94f1148774616951d973dbbfabe47f5170ddcdb991061d74e999f1a14bafdd is not running
Error response from daemon: Cannot kill container: e2b9c7f69a9c: Container e2b9c7f69a9c3c79106299f7b9ddda4a76465cf2c62c9864e1354f9111b8073c is not running
Error response from daemon: Cannot kill container: 82fbf4f23df4: Container 82fbf4f23df4c24c47d8b2c792498f4cd49fe8743df88323ea4f7b460d8ddb3b is not running
Error response from daemon: Cannot kill container: 2ca7cd673653: Container 2ca7cd67365395a665aeef26f0c12049f55195db8da81b87bcefc14d1dc93a8e is not running