GUI acceptance tests using environment deployed from packages.

Build: #2082 failed

Job: Onezone tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
13 minutes
Revision
13c8582397a5a6dbba3b40c37b28e380225c1c27
Total tests
8
Successful since
#1943 ()

Tests

  • 8 tests in total
  • 12 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  46069      0 --:--:-- --:--:-- --:--:-- 46069
Error response from daemon: Cannot kill container: ce218ebf6287: Container ce218ebf62872608bb7caee153a0b6643c589f043d21e15c1c5029b99b22578c 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-COTT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/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-COTT/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-COTT/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-COTT/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]
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
W0406 13:14:28.456905     501 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  44314      0 --:--:-- --:--:-- --:--:-- 44314
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: bc1a5f1dd98e: Container bc1a5f1dd98e820b57b62948cea3969c4e34576e08d19694f32206a2168f8944 is not running
Error response from daemon: Cannot kill container: dbb38320e01a: Container dbb38320e01a36e3f4d1918b2bf5684c1542d0075afb0959f52acfa8bea22362 is not running
Error response from daemon: Cannot kill container: 8014eb773924: Container 8014eb77392443483a4b6e18b8d48e01e0b81334c2ce7bc50bdd64674dab64d1 is not running
Error response from daemon: Cannot kill container: bcf89650ad3b: Container bcf89650ad3b8ffe560e90eff6e0b3274f5fdcc4e58cb30eef827716dd8eb862 is not running
Error response from daemon: Cannot kill container: 99d2dd28eb56: Container 99d2dd28eb5693a2ef1f4deb88d8e75bd2538722dfb517b50a692eade7fc04c4 is not running
Error response from daemon: Cannot kill container: 13cc03465367: Container 13cc0346536772fa72425c99c4aa0dc4413e773a8820365450b9a9d2cb56224f is not running
Error response from daemon: Cannot kill container: 33d3f973fe3d: Container 33d3f973fe3da6d642596c45311076158c745401839693b223ff040fa8e6c3a2 is not running
Error response from daemon: Cannot kill container: af29112a0986: Container af29112a0986c6e7292b5a5e6bdd1d0b6d1517886eacbef1bcd01728c00cf3c7 is not running
Error response from daemon: Cannot kill container: 997084a14809: Container 997084a1480958abba72ca96a5dc30e374241ba37d5d15c8f1ab4cd6600a88a5 is not running
Error response from daemon: Cannot kill container: 04a2d0218bd2: Container 04a2d0218bd2599cc14e575469014912aeb1b461eb4cb341b12ede6aeae6b2f5 is not running
Error response from daemon: Cannot kill container: 3f4c99604690: Container 3f4c99604690e35a1178a97c9b67159574e234f5d7bfc80e3483e024b8fb9251 is not running
Error response from daemon: Cannot kill container: 4d5819ea9214: Container 4d5819ea9214153cc7d52d9bc91861d34caa51557e7a267f700757ba2402640e is not running
Error response from daemon: Cannot kill container: b1cbbe78f11a: Container b1cbbe78f11a1fa974ee2f0145ee82dea1f34eba92b7e02f70f16c028cb8734c is not running
Error response from daemon: Cannot kill container: bc1d739c9f94: Container bc1d739c9f94b50c7bcd04d02f3c4f25f644b9f745f16f64efd264e0551ffb3b is not running
Error response from daemon: Cannot kill container: 46bd9dc27544: Container 46bd9dc275442c5160854df4b2645a9c32dabd634719ed177f6aa6faa9506bd4 is not running
Error response from daemon: Cannot kill container: 7ce3a2d837ce: Container 7ce3a2d837ce809d26f3ba15de900d73c4420ddc961d5002374724b929910136 is not running
Error response from daemon: Cannot kill container: bb780228b171: Container bb780228b171526ac2bae5a4f662bcb1e508a93e61ee95f881d1a92deac3623a is not running
Error response from daemon: Cannot kill container: d72456256df6: Container d72456256df6ba508a180d075d9ba0baca1ea17627abd87ed4724bc019d645b5 is not running
Error response from daemon: Cannot kill container: 88430012bbfe: Container 88430012bbfeacd610dcfda6acfa0b0d13091fc2f33d3191bb967f8be3d87164 is not running
Error response from daemon: Cannot kill container: b67ffce3141b: Container b67ffce3141b7e300e6e8924878f6c5b66562589e8a1e5599b6f97786322aafe is not running