Acceptance tests using different clients concurrently. Environment deployed from packages.

Build: #2171 was successful

Job: Access tokens id caveats was successful

Job result summary

Completed
Duration
24 minutes
Revision
178097c5f0b63cb324fc6fb80e8aba8582f6f142
Total tests
9
Successful since
#2138 ()

Tests

  • 9 tests in total
  • 22 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  45174      0 --:--:-- --:--:-- --:--:-- 45174
Error response from daemon: Cannot kill container: 61f4a5144393: Container 61f4a51443930db12ec321b57e37aa47cf8c26aadf3589936d6264a32829de65 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-MAOPT-CATIC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATIC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATIC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATIC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATIC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CATIC/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-MAOPT-CATIC/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-MAOPT-CATIC/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-MAOPT-CATIC/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
/bin/sh: 2: [[: not found
Error: could not find tiller
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
id: ‘user1’: no such user
command terminated with exit code 1
id: ‘user2’: no such user
command terminated with exit code 1
command terminated with exit code 1
command terminated with exit code 1
command terminated with exit code 1
id: ‘user1’: no such user
command terminated with exit code 1
id: ‘user2’: no such user
command terminated with exit code 1
command terminated with exit code 1
command terminated with exit code 1
command terminated with exit code 1
Defaulted container "oneclient" out of: oneclient, wait-for-onezone (init), wait-for-token-dispenser (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
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  39769      0 --:--:-- --:--:-- --:--:-- 39769
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 3ebbc5de301b: Container 3ebbc5de301b16971f406e7f1faf84b7314a52bc61bcf8a1ae763d369fe75c86 is not running
Error response from daemon: Cannot kill container: 938b5ed00726: Container 938b5ed00726e858fbc2c3c0b6ffd44442446758f7b6097b3d9844f0001b59cf is not running
Error response from daemon: Cannot kill container: 664fba93c92f: Container 664fba93c92fb668ccda2980eaa06918fc44843ceaa0aaa785f2280be53a28dc is not running
Error response from daemon: Cannot kill container: ec5c8aeaf72d: Container ec5c8aeaf72daf5ff4cc9162f2fe4e0025fba80091eb8c7d7aacfdbc84e999a9 is not running
Error response from daemon: Cannot kill container: b76dab97b2b7: Container b76dab97b2b722b6602533dc221024185c5f6e441562650ad0eeb31f4e8807bd is not running
Error response from daemon: Cannot kill container: bec242f95b70: Container bec242f95b70498dacb2f7dd143b8fbb18681894ebfda4848a083c714c467efb is not running
Error response from daemon: Cannot kill container: 09829fed533d: Container 09829fed533dfe0d176b84e1a0d952d2210d7e8f707d5005e4b20c07785762a7 is not running
Error response from daemon: Cannot kill container: 610c25b41e95: Container 610c25b41e95f0732017360651bf29f5e98f55d2f5b0b45cbc2150ab0cf1fb73 is not running
Error response from daemon: Cannot kill container: 72ecbb18ac5e: Container 72ecbb18ac5e68b4920f6c348401f84e75a8af1dc0104b51ede8e7fd05c731fc is not running
Error response from daemon: Cannot kill container: e92ee302ad18: Container e92ee302ad184e5c7945ef149a0d8dbcf17b3d15dfaa1ae5cb4005d8a3fd4638 is not running
Error response from daemon: Cannot kill container: b6ccc212f2b7: Container b6ccc212f2b7a86327dd53c92272947f8e71caa056d460f9c6083a26a3df0554 is not running
Error response from daemon: Cannot kill container: ed16aee1caeb: Container ed16aee1caebb6586be95eb848e021648baaf8356352d026547862aaa8ab9296 is not running
Error response from daemon: Cannot kill container: a6eb5e83d3c5: Container a6eb5e83d3c515eedcc534513b9b5f214bbdd6743ad56d3005c588770d8c388e is not running
Error response from daemon: Cannot kill container: 90e0f8efc437: Container 90e0f8efc43719c25e9b414b61bd90d1ead7168d2dc30159d732fbe2f133283c is not running
Error response from daemon: Cannot kill container: ade85f556c01: Container ade85f556c01e203e50ef8351914a0f00eebbed8e49374bc4114adb46547fd03 is not running
Error response from daemon: Cannot kill container: 04ebc3a6b3a6: Container 04ebc3a6b3a6738d544bbee5157daa346fe24a156c0913c3867c901be8862753 is not running
Error response from daemon: Cannot kill container: 40300d7b2058: Container 40300d7b2058c05d764f28095416a4fe09f576eab294d04d225ea1e644b97ce7 is not running