GUI acceptance tests using environment deployed from packages.

Build: #2134 failed

Job: Multiprovider basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
29 minutes
Revision
72d4158537fcbe5e765cfeaf323ebd441ede24a2
Total tests
8
Successful since
#2082 ()

Tests

  • 8 tests in total
  • 28 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  41918      0 --:--:-- --:--:-- --:--:-- 41918
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: 448d9c6d53f8: Container 448d9c6d53f83af7d279ff5c29f600d25ce4a5cdbcc1122cd5a34e53749b3806 is not running
sudo: unable to resolve host bamboo-agent-amd-01-do-not-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-CMBT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CMBT/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-CMBT/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-CMBT/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-CMBT/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-amd-01-do-not-disable
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
sudo: unable to resolve host bamboo-agent-amd-01-do-not-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]
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
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  16920      0 --:--:-- --:--:-- --:--:-- 16920
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
sudo: unable to resolve host bamboo-agent-amd-01-do-not-disable: Name or service not known
Error response from daemon: Cannot kill container: 76843b3a5c55: Container 76843b3a5c552ab49265d13d26236a6eb3a6d5e87f625162dd94058ed67f9284 is not running
Error response from daemon: Cannot kill container: bbcf10b10e6e: Container bbcf10b10e6ec448a97bb00662ee5bbdd81adc28e24901e0df75bc50b1aa90fc is not running
Error response from daemon: Cannot kill container: a48972436e64: Container a48972436e64c9554da2d96dc89886159d1a9733ed51a7f7ca45f69a7c96db22 is not running
Error response from daemon: Cannot kill container: 97427d7b17f6: Container 97427d7b17f6fed6d0ed7b271efc2597c7de4c9291f43b622103beb20608055c is not running
Error response from daemon: Cannot kill container: c695ef49ab22: Container c695ef49ab2242d04d786210a95cf799e4e09d297a5c7e27a3149a0680034b38 is not running
Error response from daemon: Cannot kill container: 58c98be5ef94: Container 58c98be5ef940733b4cc52654732284803cdbc46a0f57b07464ac8c3dba0c620 is not running
Error response from daemon: Cannot kill container: d1c0d84aeaa2: Container d1c0d84aeaa22eb9b240cfb62dcd5317ffe89d68deb09ee861d6f2ceb445b2f1 is not running
Error response from daemon: Cannot kill container: 7bb933ab0aa7: Container 7bb933ab0aa7317220e6954af3c7217bf763093deb2743c5eb23db1caffe5a1e is not running
Error response from daemon: Cannot kill container: 12a57b919f29: Container 12a57b919f296275cf3a905308e8f798f388bf1c8317c118ae345196ddb81e17 is not running
Error response from daemon: Cannot kill container: 01a2945cdea7: Container 01a2945cdea7faac93cb012a8b5035b8893d2c22868a24b941aea40f8c1f4604 is not running
Error response from daemon: Cannot kill container: 7bc2f6331e04: Container 7bc2f6331e04725964ba401766bdf2d80980ba524176783c3b3696f1f9501fe1 is not running
Error response from daemon: Cannot kill container: 4330b157fad7: Container 4330b157fad75d548220a6c64bc8bb41b66ca00125f48049b5e925eb59cdf0fa is not running
Error response from daemon: Cannot kill container: 87851b0cd5cc: Container 87851b0cd5cc21812448f86c2634f15ee35b8d813999746ea6e8baad8133cec7 is not running
Error response from daemon: Cannot kill container: 2befdd1b0585: Container 2befdd1b0585c2f089653ff47fc3930e2ee0982a24eeb35b674fbc4bcb3b9f81 is not running
Error response from daemon: Cannot kill container: 4583fbc3d7a7: Container 4583fbc3d7a7d71b435aa5080bcdc76ee643bbbc33aca7f9f819205528e26a3c is not running
Error response from daemon: Cannot kill container: 90b890e66475: Container 90b890e66475c541370293d398355d32d9aa397d8b23af376b6064561b2ebfca is not running
Error response from daemon: Cannot kill container: 444a943fcc38: Container 444a943fcc389f01758421caf36e0e9603dbbefb0d1301f3f76f34b6be215af2 is not running
Error response from daemon: Cannot kill container: ed40be2dc4bb: Container ed40be2dc4bb97b4501d9fde85aa59580eb7f086252f103e432b6bfeb055c258 is not running
Error response from daemon: Cannot kill container: c70f4cc7eab9: Container c70f4cc7eab93d9b290389f5ed6d494df291d6ada36d3821c8a732d9a301470e is not running