GUI acceptance tests using environment deployed from packages.

Build: #2143 was successful

Job: Onezone invite tokens with consumer caveats was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
22 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
Total tests
9
Successful since
#2082 ()

Tests

  • 9 tests in total
  • 21 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  47479      0 --:--:-- --:--:-- --:--:-- 47479
Error response from daemon: Cannot kill container: 655b7e0ec032: Container 655b7e0ec032abbcbf236f73e158024acfe8519a7440883f91e8fae01f8bb09c 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-COITWCC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWCC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWCC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWCC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWCC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COITWCC/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-COITWCC/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-COITWCC/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-COITWCC/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Unable to find image 'onedata/acceptance_gui:v8' locally
v8: Pulling from onedata/acceptance_gui
a1298f4ce990: Already exists
04a3282d9c4b: Already exists
9b0d3db6dc03: Already exists
8269c605f3f1: Already exists
c810ae7364ef: Already exists
78d356e6ec21: Already exists
792b20546d07: Already exists
c1d3130a77b3: Already exists
0c7ad6b015da: Already exists
114ec36e4007: Already exists
2bc588dde0c7: Already exists
89641d7ca7e2: Already exists
b6cd4b44aa19: Already exists
e1c77802a505: Already exists
f373aa611054: Already exists
Digest: sha256:97e4de524ef380ad8c07bf6c71280c378a5e0179834942ff0e6c0007d32b148c
Status: Downloaded newer image for onedata/acceptance_gui:v8
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
W0518 20:35:32.550950     490 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  48468      0 --:--:-- --:--:-- --:--:-- 48468
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: fc189a4f709f: Container fc189a4f709f266641cadd5efa7789620dce9f9f6c939780d21a6e27dce3f817 is not running
Error response from daemon: Cannot kill container: f5f4206efe96: Container f5f4206efe96dd317564955bfeb860db8fb49faa4a5fd6c8bc5ab262ca509b1f is not running
Error response from daemon: Cannot kill container: c407775139ce: Container c407775139cea7a40a7f6eb0624510d7974f1ac710e3195c5044a726ae410032 is not running
Error response from daemon: Cannot kill container: a60c3865e5d8: Container a60c3865e5d80c62b0dd1eb03a85fd35d3cda7d2ace8c9d7b289e65fc3ae3299 is not running
Error response from daemon: Cannot kill container: 976b3f59f8ec: Container 976b3f59f8ecca9f3c07e1fd5169776d12afcab586653508a4bfab1b4a100c00 is not running
Error response from daemon: Cannot kill container: 72bb82a68342: Container 72bb82a68342a2162e723f8832123b286cfddc1dc9eceb153fb34743879e9c74 is not running
Error response from daemon: Cannot kill container: 6b81ead2ef66: Container 6b81ead2ef665f049af7355ba5c1f0a300398c2605c5593339fccceac2b59e9c is not running
Error response from daemon: Cannot kill container: 74b2cc62e4a3: Container 74b2cc62e4a3e49669adf84d56d2b66e74f02992a586d439c98f693e8dbf51a7 is not running
Error response from daemon: Cannot kill container: c8fd6e3b2bd3: Container c8fd6e3b2bd30fea02ed16c58c2141fc7e3b389b23fe99b5238d3ba80784287c is not running
Error response from daemon: Cannot kill container: ed82da4fc212: Container ed82da4fc212ab2102b7948c3b87b7fe7fabf2a45cfb4a2bed58d24ce4374184 is not running
Error response from daemon: Cannot kill container: 50388cebcbf1: Container 50388cebcbf1c64f43d6fd20c881d7542c6b66c6ff32a03f05c0623bd90345bd is not running
Error response from daemon: Cannot kill container: 173aefb96c07: Container 173aefb96c076098769005934ea88ad1dd3731f17f306f3c2268999c99502955 is not running
Error response from daemon: Cannot kill container: 2fcfc5bbb3bb: Container 2fcfc5bbb3bbd571a544359cec0041b35b992af1029eb0d16c44a042bd1896a2 is not running
Error response from daemon: Cannot kill container: 58516071d3c9: Container 58516071d3c9a4ab9119679c816728aa808cb22a522327c68924d3956becbc27 is not running
Error response from daemon: Cannot kill container: 1d6672913ea6: Container 1d6672913ea621dec9d17bab8acb213561e1e5fe0e5f0fb5382efd91a3a41890 is not running
Error response from daemon: Cannot kill container: c6a506b30463: Container c6a506b30463d0860becc9d5d076cb69845da074f772b23b9ec2cd67d919d6b2 is not running
Error response from daemon: Cannot kill container: d6a26b1dff29: Container d6a26b1dff296aa380182bb235d0a22e6ddf4e36aac94ee949f2fcd38e4d99ed is not running
Error response from daemon: Cannot kill container: d8abd470704e: Container d8abd470704e614f498f9d41d8c66afe5d4475882c89c67154f5a1864d9028dc is not running
Error response from daemon: Cannot kill container: 66956d96ba1f: Container 66956d96ba1fab5b2e70a3aa2206e8a63ec86c37fa72e0f5adf4c8802cb0008e is not running
Error response from daemon: Cannot kill container: d07ae88a6a85: Container d07ae88a6a85c27ff921089a990349faf2028988f6a4f5eb3fb98199506325c5 is not running