GUI acceptance tests using environment deployed from packages.

Build: #2099 failed

Job: Onezone invite tokens with caveats was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
17 minutes
Revision
069664170b01b34f9742ffb53de1c68131c0e582
Total tests
4
Successful since
#1958 ()

Tests

  • 4 tests in total
  • 16 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  38775      0 --:--:-- --:--:-- --:--:-- 38775
Error response from daemon: Cannot kill container: 3b22dcc40504: Container 3b22dcc4050415736c146184091f92bacfc78ebb41fd4ed65db6619393864d99 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-COITWC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWC/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-COITWC/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-COITWC/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-COITWC/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
W0413 17:45:59.820846     486 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  26895      0 --:--:-- --:--:-- --:--:-- 26895
Error response from daemon: Cannot kill container: c1360bfddaa4: Container c1360bfddaa4fd871aa25a43587d950e705343f2d7963aa783b5509721e54b0f is not running
Error response from daemon: Cannot kill container: 5ed6a9792a18: Container 5ed6a9792a18a364d46029fd443426d2e8ab1740a75b75ecd2810538b4e18cb5 is not running
Error response from daemon: Cannot kill container: 2ffdd03fbda3: Container 2ffdd03fbda3b8193f259649b73e7ccf47758bd184ba65de418156f91817ed0f is not running
Error response from daemon: Cannot kill container: bf2cca4c53ca: Container bf2cca4c53ca19d28ae7c92a8c68c92ba18f5031e54aeb54ebb049e46e24ac13 is not running
Error response from daemon: Cannot kill container: d0ce55c779ee: Container d0ce55c779ee13df1dd8040a34efdc4dd357b9388449fa716b7c25ba22a3313b is not running
Error response from daemon: Cannot kill container: cf63cf85c592: Container cf63cf85c592cd4e685aa73cb144ed1c3caf30ef6272c2b7f8d61fb431e4d922 is not running
Error response from daemon: Cannot kill container: 76dc87d920da: Container 76dc87d920da01a58bcb3d877626c30f37fce4edaf421a12beb787387bddf61f is not running
Error response from daemon: Cannot kill container: f9d23ac95a6e: Container f9d23ac95a6e883ab36275c57bdd2815ff1e38c651568db7bf3615520f1e11b4 is not running
Error response from daemon: Cannot kill container: b4319663be68: Container b4319663be68a26c911d50b915c320b3a3a16f096414d9238be8c6b1707337c8 is not running
Error response from daemon: Cannot kill container: c1607deb1c29: Container c1607deb1c2983cbf6abe53f7ba12d0785b1951922f1c40f9dbfb76c4145b48b is not running
Error response from daemon: Cannot kill container: 4031451c4dd0: Container 4031451c4dd0879888baaeba177b739c972a12bc0a633bca8c5203aead10d4ab is not running
Error response from daemon: Cannot kill container: e4e3d53a1557: Container e4e3d53a1557331f474cfea83738227a04ffd200ec130addcfb5cec842e1b34b is not running
Error response from daemon: Cannot kill container: 3d1c995a7831: Container 3d1c995a78311fb3eb0a676cf82de7780b33d8175ab987017321187d9d1eb59c is not running
Error response from daemon: Cannot kill container: 1f97fc780a81: Container 1f97fc780a8171db0f9e519001be9509a5a4e76b46833e809b96e0194a574a55 is not running
Error response from daemon: Cannot kill container: 02244843bf36: Container 02244843bf362e9a8888a911b021996cd90e7eafbcf7a633d096f861a89d2b6e is not running
Error response from daemon: Cannot kill container: 9c4344d1361a: Container 9c4344d1361a2a7c2ac2a330576dffe4ce1ecfadab6f8bdf85fe32229a0e0c15 is not running
Error response from daemon: Cannot kill container: 64f13b88a990: Container 64f13b88a9909e6d6a285929c9f457473a7b89a8b98d2cbe595a968a3c968bc3 is not running
Error response from daemon: Cannot kill container: 56345b181864: Container 56345b1818648ff0a6e2c5fd1d1a448264baf5a4863515dcdf994dfe93a19bde is not running
Error response from daemon: Cannot kill container: c0e26a91713f: Container c0e26a91713f88731f061ac499d8a6a119b3f95b811356cdc0ac711b7e30808e is not running
Error response from daemon: Cannot kill container: 105723e46476: Container 105723e464760db8001ae51aaf093e455ccca8fec48779b467c02b8d0d957ffb is not running