GUI acceptance tests using environment deployed from packages.

Build: #1325 failed

Job: Onepanel deployment basic was successful

Job result summary

Completed
Duration
4 minutes
Revision
caeaf9d1968c93b33829e924857a43044dd3967c
Total tests
1
Successful since
#1323 ()

Tests

  • 1 test in total
  • 3 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  4419  100  4419    0     0  14355      0 --:--:-- --:--:-- --:--:-- 14394
Error response from daemon: Cannot kill container: f7b94a57df00: Container f7b94a57df00acf569c541004b4d372691ece33ebe37e44ff3978ce5ba643631 is not running
tput: unknown terminal "unknown"
Cloning into 'bamboos'...
Cloning into 'cdmi_swagger'...
Cloning into 'one_env'...
Cloning into 'onepanel_swagger'...
Cloning into 'bamboos'...
Cloning into 'oneprovider_swagger'...
Cloning into 'bamboos'...
Cloning into 'onezone_swagger'...
Cloning into 'bamboos'...
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error: Could not create /home/bamboo/.helm: mkdir /home/bamboo/.helm: permission denied
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
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  4419  100  4419    0     0  13910      0 --:--:-- --:--:-- --:--:-- 13940
Error response from daemon: Cannot kill container: 855aabd1bbea: Container 855aabd1bbea152ba3d356d42c9c112a992ee9bada934f1374c923e54785f581 is not running
Error response from daemon: Cannot kill container: 6595322bbd09: Container 6595322bbd094ea4c28c32036b1307b51d00763b98514145aaa21c70c50000c1 is not running
Error response from daemon: Cannot kill container: 45c86b733617: Container 45c86b7336175eb3d841b87a55d8b7e4a8d74af248dbe9afcf72008179f5010b is not running
Error response from daemon: Cannot kill container: 8df5f917402c: Container 8df5f917402cb4cfb9aeaaf26bac8c969e78315fad303c772c17856063734b1e is not running
Error response from daemon: Cannot kill container: d694e1d3d921: Container d694e1d3d921bf03913820dc9bd59a2edb622661ec8c9d6089d0abc6fdf7cff2 is not running
Error response from daemon: Cannot kill container: 8e6aea338e05: Container 8e6aea338e056e9d6376ad0a169e12d8ff529d34a8346e4320847cb8d2cddb37 is not running
Error response from daemon: Cannot kill container: 1f586e89e0e3: Container 1f586e89e0e3469a1a699d19f3ff7cdf1a91e3357e8e9301e1ecb32695d8cf33 is not running
Error response from daemon: Cannot kill container: 22ad0594bfd6: Container 22ad0594bfd630468d0fffd5349ca2d83723af2bd98cca7cdd81f35627e5e676 is not running
Error response from daemon: Cannot kill container: e6a3b2dca763: Container e6a3b2dca7632522cbac649e80eab56c2bf5642c2ddcb588d15429aed2278ace is not running