GUI acceptance tests using environment deployed from packages.

Build: #2140 failed

Job: Onezone tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
13 minutes
Revision
dfd405a02fa2a4bab1ba6431bc2638a43a9cd1cb
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  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: bf01dcd385b4: Container bf01dcd385b4dad5b0e662fc07e4fcd1bd1ce203c983344be0c1fa5c13497271 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-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
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
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
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]
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
W0516 20:30:01.914428     500 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  45174      0 --:--:-- --:--:-- --:--:-- 45617
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
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: 57f178238f56: Container 57f178238f56ac5e641401cd22fcc71ef31e6532712276a45fab8aaafdf422ac is not running
Error response from daemon: Cannot kill container: 6621670b3ce9: Container 6621670b3ce912637064ef5393003ab580240be0ef007c128fcfc34f10d33820 is not running
Error response from daemon: Cannot kill container: 23a1371dc7c0: Container 23a1371dc7c07dc9ff4bcc845efb86b7f7a950228526446db0229b87791cdc37 is not running
Error response from daemon: Cannot kill container: 3168c062c68d: Container 3168c062c68d613dcdcdcd74ef5b4f08b26f622492c44eb8a23ea77a10fa7f16 is not running
Error response from daemon: Cannot kill container: ba2169724dad: Container ba2169724dad6936300f371ed1fd8a9baeae9a1f30fe8f6cb3a2c39645b04ffd is not running
Error response from daemon: Cannot kill container: f79831e0c6eb: Container f79831e0c6ebf19d6476287e9a11dfc7acd2f8ffa867e4539b7db6ad9a48e659 is not running
Error response from daemon: Cannot kill container: eb09556ed389: Container eb09556ed3892e64a097f23dd3ae24697f17949773a3f81fbe440b58a936e7e0 is not running
Error response from daemon: Cannot kill container: d6fd6dcd6bbe: Container d6fd6dcd6bbe8114dd299d4fddc1baee54fbfeb800172bb88ecd4de925b7241c is not running
Error response from daemon: Cannot kill container: d6e8a51d40a4: Container d6e8a51d40a4d91c994361dbf3725cba2d1e8a85a43c7a599ba0bba098d7e83f is not running
Error response from daemon: Cannot kill container: 181141c8f612: Container 181141c8f612e7d61d524147fc08afb1742ddec8bc058d542ca918a7062ec8e6 is not running
Error response from daemon: Cannot kill container: 0cdbee0b1618: Container 0cdbee0b1618d398e1ab876161943235f4dcb5fc4eb2b92794391e03c06ba379 is not running
Error response from daemon: Cannot kill container: ed123062b3ee: Container ed123062b3ee2983029f9f56a49865b2e875423103f4d49a5be2039a895cdb6c is not running
Error response from daemon: Cannot kill container: 0654e71245d1: Container 0654e71245d1378ef1ab51160a3d0086fd264796f47195ac8372dd1777cb73ba is not running
Error response from daemon: Cannot kill container: 4a34e0abdbd1: Container 4a34e0abdbd119559e52d57662d0c727f54770a5e151146b466a5ded834bb177 is not running
Error response from daemon: Cannot kill container: 53d2693da825: Container 53d2693da825863440dea14e84bcb04424fe7195053c31e220b0ba26ea077ea3 is not running
Error response from daemon: Cannot kill container: e1594c8a2c5e: Container e1594c8a2c5e8ffc51e9bdf7520fc283416e4aaee37c84260775d2ac5a0f91fa is not running
Error response from daemon: Cannot kill container: 4e768a435159: Container 4e768a43515923494c098a6110d7dd6119868c3eb7a66d8a2916f84f445aadd5 is not running
Error response from daemon: Cannot kill container: 0ce6a0e9c756: Container 0ce6a0e9c75628055156cd1b319ef56cb050dbe06f55c613d688815ff06df961 is not running
Error response from daemon: Cannot kill container: c691e876b0e3: Container c691e876b0e32fb08cd40a8edf67c975f11d7b12c6cedea16b7ebbd0eee30e10 is not running
Error response from daemon: Cannot kill container: 7cd34d6c3eab: Container 7cd34d6c3eab72e89ab0a366ad5db7c71510d394b63ebb23720ad27a347528b4 is not running