GUI acceptance tests using environment deployed from packages.

Build: #1328 was successful

Job: Chrome onepanel deployment ceph was successful

Job result summary

Completed
Duration
5 minutes
Revision
912c82abf17a8bbd266d0fa0c63c0fdbfa50afe8
Total tests
1
Successful since
#1323 ()

Configuration changes

Job Chrome onepanel deployment ceph with key ODSRV-GAPT-CODC no longer exists.

Tests

  • 1 test in total
  • 4 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  15875      0 --:--:-- --:--:-- --:--:-- 15895
Error response from daemon: Cannot kill container: 39d5571171e0: Container 39d5571171e0fa35a6f5c3016e2542f92a010a52fef19d6212f2d259b40ca687 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4419  100  4419    0     0  16136      0 --:--:-- --:--:-- --:--:-- 16127
Error response from daemon: Cannot kill container: 9feb8f082d74: Container 9feb8f082d74094cc73acfb5293152a39697cd569428e724d43afd27d2b794f2 is not running
Error response from daemon: Cannot kill container: 1497214007da: Container 1497214007da32ad40c82ae0de3a7c6daf19b3cd8239d00af5b304e2bc04c4f6 is not running
Error response from daemon: Cannot kill container: 8a469ea30048: Container 8a469ea30048f6491b8bd7f27069f79c9f75508fc552861f9d57044262755fda is not running
Error response from daemon: Cannot kill container: 1f49c53ba7a2: Container 1f49c53ba7a24b1e13b0d83fae74aad317a9e7ba92be3875947c8c5a822c48c2 is not running
Error response from daemon: Cannot kill container: d7f985075a28: Container d7f985075a28706466083c8346f968fd5c2937fa35dd40e3057e6460bf566905 is not running
Error response from daemon: Cannot kill container: c38f49001101: Container c38f49001101d36654b89fea57f802f333d02022191629da7916dd4165fae01b is not running
Error response from daemon: Cannot kill container: f46d551ea905: Container f46d551ea905c75a23a40642883642214a851d82476cb7b5afa114d2dba591b5 is not running
Error response from daemon: Cannot kill container: 42f2eecec197: Container 42f2eecec1974db2a8560fb996c40642f74658a6703d0d79ecd0b98c19d05cf8 is not running
Error response from daemon: Cannot kill container: 26a7bc132fb0: Container 26a7bc132fb075553f6c6e136484de06e2481efcec7ad41ee250e9931f4920b2 is not running
dmsetup remove osd--f2091f77--8a7e--428f--8972--9ee66eca4ac4-osd--data--f2091f77--8a7e--428f--8972--9ee66eca4ac4