GUI acceptance tests using environment deployed from packages.

Build: #2145 was successful

Job: Oneprovider upload was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
17 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
Total tests
7
Successful since
#2112 ()

Tests

  • 7 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  47000      0 --:--:-- --:--:-- --:--:-- 47000
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable: Name or service not known
Error response from daemon: Cannot kill container: 04c14312d533: Container 04c14312d533578fa12cadd5ba6635408fac7a08577dc259b4e0563669c3ec9e is not running
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable: Name or service not known
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
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable
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
W0523 12:50:57.206128     455 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  35792      0 --:--:-- --:--:-- --:--:-- 35519
sudo: unable to resolve host bamboo-agent-os-03-s3-proxy-dont-disable: Name or service not known
Error response from daemon: Cannot kill container: f6baa3d238f4: Container f6baa3d238f419df40789aebe72542070feb091bf1ec02b9c58a8ae696ff1225 is not running
Error response from daemon: Cannot kill container: d3c426fcbce0: Container d3c426fcbce00d5df4d7e0d5775577e92b3d8f0f311c6491671eee8ae9188928 is not running
Error response from daemon: Cannot kill container: c89d972a6ca5: Container c89d972a6ca521d5188bb69881249c86704232062970ea654cbaeb1ed29321fc is not running
Error response from daemon: Cannot kill container: 3428df641294: Container 3428df64129481ee24ce4da72d5b21d86cf6c51199eb586d3e53400a26e05b44 is not running
Error response from daemon: Cannot kill container: aa709c23b976: Container aa709c23b976039e78fd1a7dc64d6d268b778e0e2b08e2a4fdff831d14941251 is not running
Error response from daemon: Cannot kill container: 74a3800db8f1: Container 74a3800db8f12188f90c620b78175f33d1d9e37fb04caeafd9a2e18eadcc1f5f is not running
Error response from daemon: Cannot kill container: 4c1d00f7a04f: Container 4c1d00f7a04fc716c86cefdc9866cb7cdfd0719f65f30dfe2f417434114d32b1 is not running
Error response from daemon: Cannot kill container: fcad9c7c9790: Container fcad9c7c97904cf46e9a17b112018b611c7a1f7b0a45dc74ecb06ba0e5951d3c is not running
Error response from daemon: Cannot kill container: e3b6f787b7c5: Container e3b6f787b7c507b92989f3d89b49340d33e27bc9a545c9e1d3fa6117800c6da1 is not running
Error response from daemon: Cannot kill container: f417fe90dbd8: Container f417fe90dbd8fd6ad0290340769866a11b8689679f651bab48456c1394a36b70 is not running
Error response from daemon: Cannot kill container: a2c74b4bea25: Container a2c74b4bea25a125c50a2b6b063a1145f598c32dbbdac1d64bf210455bd125b9 is not running
Error response from daemon: Cannot kill container: dec9e3b2c7f9: Container dec9e3b2c7f99e0df03c84e9eeb0dc014c8bbf8d45e5519147168cfc4aa1777f is not running
Error response from daemon: Cannot kill container: 073951e90caf: Container 073951e90caf33a3e9982dddcc9ab04a4aa0deea0e91a42f5808952e475ac4ff is not running
Error response from daemon: Cannot kill container: 7ab7044fdc14: Container 7ab7044fdc145261aa8d1157316b1bbba2f852fb90f4a4ce910baa34fe972113 is not running
Error response from daemon: Cannot kill container: afed62bd36e5: Container afed62bd36e51dbabfa1892a3447e97579c0dbf283b3b16a4d685af1819097dc is not running
Error response from daemon: Cannot kill container: ae283caef75b: Container ae283caef75bb1c4c67c04a86735173c00c9877e1a16eac94da3693be7d4c173 is not running