GUI acceptance tests using environment deployed from packages.

Build: #2163 was successful

Job: Onezone harvesters memberships privileges was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
14 minutes
Revision
2a6ac951983b0da397726653daa1ebcdbbe74ca8
Total tests
5
Successful since
#2112 ()

Tests

  • 5 tests in total
  • 13 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  48468      0 --:--:-- --:--:-- --:--:-- 48468
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: 73b5b5cdba44: Container 73b5b5cdba44d6ab1160e74fa1c681708264fc77d9a366d3730f439fdda38b7c 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-COHMP/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHMP/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHMP/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHMP/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHMP/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHMP/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-COHMP/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-COHMP/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-COHMP/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
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
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
W0603 19:47:12.978524     439 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  46530      0 --:--:-- --:--:-- --:--:-- 46530
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: ac2af6bd9fe3: Container ac2af6bd9fe34e2f47e0d8d0f3da8b0605db815731b904ac660c16243b62286f is not running
Error response from daemon: Cannot kill container: dc8583a7ffc5: Container dc8583a7ffc51eccd3fea4e386023c862821f5f686188abe52d4580069b3e662 is not running
Error response from daemon: Cannot kill container: e9331c6bb02e: Container e9331c6bb02e4772b7b4ddbca21d7ba98b4aee924dba94923fc7c590e85f9ff8 is not running
Error response from daemon: Cannot kill container: ea18687faf5e: Container ea18687faf5e46c49c90b732cfcde29a33cf02bb94ddab70134fd24cb5b71104 is not running
Error response from daemon: Cannot kill container: 093a1eb0f422: Container 093a1eb0f4221aa87734d48aa571e7c4d20b7f22baa563e64421129c21b5904f is not running
Error response from daemon: Cannot kill container: 568d9066e6ca: Container 568d9066e6ca8b49b215a11551db0420e2192b5f4add3ee7cdc5cbd57935cc77 is not running
Error response from daemon: Cannot kill container: 8ae12767cabd: Container 8ae12767cabdb9d2f4096dc22d12ca12762b5be3d27f04f0b3eb1d8d81374bff is not running
Error response from daemon: Cannot kill container: 272b5898fae1: Container 272b5898fae1839773dc7faad09fb87b9d9b57fccf0fe359ba79d9db25351bab is not running
Error response from daemon: Cannot kill container: 2bc33ed54700: Container 2bc33ed5470051caa6fab22ad2531189f5d78102a861be3eeace29fd1307d14a is not running
Error response from daemon: Cannot kill container: 56c7ec93c659: Container 56c7ec93c65950b168b8f7c2d2762b0ba9df6c21ad72134489292e9142f210b5 is not running
Error response from daemon: Cannot kill container: 06abccc85ade: Container 06abccc85adec77bb971e1a5348c2014481766905ef7d7959d6b923a9781e976 is not running
Error response from daemon: Cannot kill container: 554bfa5ac9e9: Container 554bfa5ac9e9653e7197dd8988e98541a17019a78075d20011692dd164b3e379 is not running
Error response from daemon: Cannot kill container: ff6672558f46: Container ff6672558f46bc83fe5c80197a0c11b456f339b4d445ac8b87f9093b53be0d01 is not running
Error response from daemon: Cannot kill container: 6f6e25948f89: Container 6f6e25948f89fe5bfecff4c69300dda319219dd65139f8670b716b0502340452 is not running
Error response from daemon: Cannot kill container: 4abeadae1e90: Container 4abeadae1e90e1dc66c766f051caedc1934ffa35d6c602af0043abf1067fd4ca is not running
Error response from daemon: Cannot kill container: 2c454608f8e1: Container 2c454608f8e19e5a1e615c614a11a2001528258921b989e5343812a132ad81ae is not running