GUI acceptance tests using environment deployed from packages.

Build: #2135 was successful

Job: Onezone invite tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
45 minutes
Revision
72d4158537fcbe5e765cfeaf323ebd441ede24a2
Total tests
9
Successful since
#2082 ()

Tests

  • 9 tests in total
  • 44 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  43485      0 --:--:-- --:--:-- --:--:-- 43485
Error response from daemon: Cannot kill container: 397f172e7b49: Container 397f172e7b49a515af96133ac0bd57369a943ebe151c748ce113f69938689804 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-COIT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COIT/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-COIT/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-COIT/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-COIT/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
W0509 11:58:02.924698     494 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  17692      0 --:--:-- --:--:-- --:--:-- 17692
Error response from daemon: Cannot kill container: dc6ce216e78e: Container dc6ce216e78e63648ba13f0fc2bf083b5417a9b5774a162ee19d869bdc592f9e is not running
Error response from daemon: Cannot kill container: 1f69a758c056: Container 1f69a758c056602acd620f73179664bde8263a82ca948d37746665e3e0b897c6 is not running
Error response from daemon: Cannot kill container: 64373948067e: Container 64373948067ef50240569b79d1a1329570a62c55a57e773286a68c861e3ea4f5 is not running
Error response from daemon: Cannot kill container: ae1fbf9ad6e0: Container ae1fbf9ad6e0edc27e5d6b01293f267f35508a51cb213ee6ee3930e7eb1207d3 is not running
Error response from daemon: Cannot kill container: c7735b1ad399: Container c7735b1ad39904c5b1afc440334f1d972467babcfcdc97663ed3fd4d43f419e1 is not running
Error response from daemon: Cannot kill container: dcb4d73e0117: Container dcb4d73e011700bf7158e7b1537f1e13a0e3e9d9d5bc06d849cbadf49c0b4019 is not running
Error response from daemon: Cannot kill container: c7899e6dc9ba: Container c7899e6dc9ba8a6ea2f8d826ffbfc75af6c903ef49072d91d0aed1b1546ac59d is not running
Error response from daemon: Cannot kill container: 8cb1279135b5: Container 8cb1279135b5a94480cc4006c019d7fe3e222b13c6a747a073aff5a7da2d79b2 is not running
Error response from daemon: Cannot kill container: 78ca2fd5e1b5: Container 78ca2fd5e1b5f3b4e24bc31d062a1b35d427bd96e09eeae1de482a4f1dfd0e94 is not running
Error response from daemon: Cannot kill container: 1bd7a7e78825: Container 1bd7a7e78825ba108a7f0ad4d14088b4f201d80f156c8afa91f02e7e6f8dfc41 is not running
Error response from daemon: Cannot kill container: a74a4f8b11e7: Container a74a4f8b11e77df98bfcb3a07fbb5ecf73126237bd4b7f560e9832fb5b1c501e is not running
Error response from daemon: Cannot kill container: 6b959baf8440: Container 6b959baf8440f99f36680116fcef752712917983d3dcd2b20c9dffebdb8af00f is not running
Error response from daemon: Cannot kill container: 28036d0072ac: Container 28036d0072ac2d134bc04d1e40a3d90d085d0e68c4cff578a2533382a2f19b76 is not running
Error response from daemon: Cannot kill container: de949fc58ee4: Container de949fc58ee4a85fd52b27b77c1c9be057edfd8f375ee7c8ac4d282df39c4aa6 is not running
Error response from daemon: Cannot kill container: e129e3337f40: Container e129e3337f40faa89e5f56ee79d10898318b67f514fc290896386ee2acb6da46 is not running
Error response from daemon: Cannot kill container: da9b336cdb1c: Container da9b336cdb1c3fb60ab328af6982a29df9b6889cd31fca515db332a7568be505 is not running
Error response from daemon: Cannot kill container: d419e7c2431a: Container d419e7c2431ac5de021702297015ad159501d991936e6235b1a2b5b4cb249ed8 is not running
Error response from daemon: Cannot kill container: 5b67832d65d1: Container 5b67832d65d15dd0d6867f264a923b95bbe6f58f63629254fbf158bfd6754ceb is not running
Error response from daemon: Cannot kill container: caaa922e02ea: Container caaa922e02eadf173fbbe119115b0563e5b0c8f11ac452efe853c5ef95ce918c is not running
Error response from daemon: Cannot kill container: 799f4a4521e3: Container 799f4a4521e33a1441187817936c6cb2d2207e63ad6aaa9ff1ddbe4fb69795fc is not running