GUI acceptance tests using environment deployed from packages.

Build: #1644 failed

Job: Onezone tokens failed

Job result summary

Completed
Duration
10 minutes
Revision
8ef115ec7d87053dbcde4b51692c10279a72317d
Total tests
36
Fixed in
#1716 (Rebuilt by Michal Orzechowski)
No failed test found. A possible compilation error occurred.

Tests

  • 36 tests in total
  • 36 tests were quarantined / skipped
  • 59 seconds 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  4658  100  4658    0     0  26617      0 --:--:-- --:--:-- --:--:-- 26770
Error: unknown flag: --purge
Error response from daemon: Cannot kill container: 4b930eec3f6b: Container 4b930eec3f6b4bd2e4beb817f85f2f3b2aa547803095f519573139764583f0b1 is not running
Error response from daemon: Cannot kill container: de16d8b6c01e: No such container: de16d8b6c01e
Error: No such container: de16d8b6c01e
Error response from daemon: Cannot kill container: c6a84664430f: No such container: c6a84664430f
Error: No such container: c6a84664430f
Error response from daemon: Cannot kill container: 1c848a6aee35: No such container: 1c848a6aee35
Error: No such container: 1c848a6aee35
Error response from daemon: Cannot kill container: b71e69bce463: No such container: b71e69bce463
Error: No such container: b71e69bce463
Error response from daemon: Cannot kill container: b0ea8b639f9b: No such container: b0ea8b639f9b
Error: No such container: b0ea8b639f9b
Error response from daemon: Cannot kill container: 79e13cc3e2a9: No such container: 79e13cc3e2a9
Error: No such container: 79e13cc3e2a9
Error response from daemon: remove 6f84d3770a26f02a1b70289143ce131a60bd4c25e1fb2ed317254e99555b79cc: volume is in use - [58c6e78d93cf4c3b8f3fefac30b7445417a886d5fd9f3a91ecb52291974bd18a]
Error response from daemon: remove 23b1a619bce4c83b7a7fc7775517e2af481e08e0a859d1977dac0a6ed8caab84: volume is in use - [10beef498dc207658459161b19f6371f644c51c632a7611471ee7f7458adb783]
Error response from daemon: remove 91fe34f05aafcbd3b4ec4a62efccf7c5644652a754da630178354d55796005be: volume is in use - [6d7b9af8e9bdb6a098adb4ab2b524cddd673aef8dc10950ba708fb424c34e667]
Error response from daemon: remove 557c61a9a7822e22c501bfc14565ded2cc3a3f67f2d37834ef07fdb1e0997005: volume is in use - [58c6e78d93cf4c3b8f3fefac30b7445417a886d5fd9f3a91ecb52291974bd18a]
Error response from daemon: remove 874764ffe941af09157fd20de470926ec01000bf99b2cdf39179f4b47ba06b6c: volume is in use - [c1c215c903ac6fc7671408538ce8688780203d244f49966ca42282defb33a970]
Error response from daemon: remove b47cef159e68ce29b41ec60f7b46ec6f03c93e03f91fb63a1e5a8671bae29365: volume is in use - [4ef3105eeb8eea10088af6c2efcb64bc3dd62e3341acdbb32b3460d16819736a]
Error response from daemon: remove bc3de37bd057829099485c1b43a95d030604a55a0c5d1acece0de3739c630169: volume is in use - [c1c215c903ac6fc7671408538ce8688780203d244f49966ca42282defb33a970]
Error response from daemon: remove c2bcc22289cb679ead958af9de05625458356ef1cdf60fa56a360b557134253e: volume is in use - [4ef3105eeb8eea10088af6c2efcb64bc3dd62e3341acdbb32b3460d16819736a]
Error response from daemon: remove ff888de7c8790392a93271dfbb3e8babb50f565ede0a80dc9e40c55570e02695: volume is in use - [10beef498dc207658459161b19f6371f644c51c632a7611471ee7f7458adb783]
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-COTT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/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-COTT/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-COTT/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-COTT/onedata/onezone_swagger/bamboos'...
version.BuildInfo{Version:"v3.5.1", GitCommit:"32c22239423b3b4ba6706d450bd044baffdcf9e6", GitTreeState:"clean", GoVersion:"go1.15.7"}
NAME        NAMESPACE        REVISION        UPDATED                                        STATUS          CHART                                   APP VERSION
dev         default          1               2021-08-04 11:17:06.603480028 +0000 UTC        deployed        cross-support-job-3p-0.2.17-rc39        19.02.1   
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error: could not find tiller
Error: could not find tiller
Error: could not find tiller
version.BuildInfo{Version:"v3.5.1", GitCommit:"32c22239423b3b4ba6706d450bd044baffdcf9e6", GitTreeState:"clean", GoVersion:"go1.15.7"}
NAME        NAMESPACE        REVISION        UPDATED                                        STATUS          CHART                                   APP VERSION
dev         default          1               2021-08-04 11:17:06.603480028 +0000 UTC        deployed        cross-support-job-3p-0.2.17-rc39        19.02.1   
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
version.BuildInfo{Version:"v3.5.1", GitCommit:"32c22239423b3b4ba6706d450bd044baffdcf9e6", GitTreeState:"clean", GoVersion:"go1.15.7"}
NAME        NAMESPACE        REVISION        UPDATED                                        STATUS          CHART                                   APP VERSION
dev         default          1               2021-08-04 11:17:06.603480028 +0000 UTC        deployed        cross-support-job-3p-0.2.17-rc39        19.02.1   
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Traceback (most recent call last):
  File "/usr/local/bin/onenv", line 104, in <module>
    main()
  File "/usr/local/bin/onenv", line 98, in main
    module.main()
  File "/usr/local/lib/one_env_engine/scripts/onenv_up.py", line 243, in main
    gui_pkg_verification=up_args.gui_pkg_verification
  File "/usr/local/lib/one_env_engine/scripts/onenv_up.py", line 55, in deploy_env
    local_chart_path, debug, dry_run)
  File "/usr/local/lib/one_env_engine/scripts/utils/deployment/scenario_runner.py", line 161, in run_scenario
    stderr=subprocess.STDOUT)
  File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/bin/bash', '-c', '/yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-12.04.41/scenarios/scenario-1oz-2op/ScenarioValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-12.04.41/scenarios/scenario-1oz-2op/ScenarioValues.yaml.unanchored ; /yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-12.04.41/scenarios/scenario-1oz-2op/GeneratedValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-12.04.41/scenarios/scenario-1oz-2op/GeneratedValues.yaml.unanchored ;  helm repo update; helm install dev onedata/cross-support-job-3p --namespace default -f /home/bamboo/.one-env/deployments/2021.08.04-12.04.41/scenarios/scenario-1oz-2op/ScenarioValues.yaml.unanchored -f /home/bamboo/.one-env/deployments/2021.08.04-12.04.41/scenarios/scenario-1oz-2op/GeneratedValues.yaml.unanchored --version 0.2.17-rc39']' returned non-zero exit status 1.
version.BuildInfo{Version:"v3.5.1", GitCommit:"32c22239423b3b4ba6706d450bd044baffdcf9e6", GitTreeState:"clean", GoVersion:"go1.15.7"}
NAME        NAMESPACE        REVISION        UPDATED                                        STATUS          CHART                                   APP VERSION
dev         default          1               2021-08-04 11:17:06.603480028 +0000 UTC        deployed        cross-support-job-3p-0.2.17-rc39        19.02.1   
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Traceback (most recent call last):
  File "/usr/local/bin/onenv", line 104, in <module>
    main()
  File "/usr/local/bin/onenv", line 98, in main
    module.main()
  File "/usr/local/lib/one_env_engine/scripts/onenv_up.py", line 243, in main
    gui_pkg_verification=up_args.gui_pkg_verification
  File "/usr/local/lib/one_env_engine/scripts/onenv_up.py", line 55, in deploy_env
    local_chart_path, debug, dry_run)
  File "/usr/local/lib/one_env_engine/scripts/utils/deployment/scenario_runner.py", line 161, in run_scenario
    stderr=subprocess.STDOUT)
  File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/bin/bash', '-c', '/yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-12.04.55/scenarios/scenario-1oz-2op/ScenarioValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-12.04.55/scenarios/scenario-1oz-2op/ScenarioValues.yaml.unanchored ; /yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-12.04.55/scenarios/scenario-1oz-2op/GeneratedValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-12.04.55/scenarios/scenario-1oz-2op/GeneratedValues.yaml.unanchored ;  helm repo update; helm install dev onedata/cross-support-job-3p --namespace default -f /home/bamboo/.one-env/deployments/2021.08.04-12.04.55/scenarios/scenario-1oz-2op/ScenarioValues.yaml.unanchored -f /home/bamboo/.one-env/deployments/2021.08.04-12.04.55/scenarios/scenario-1oz-2op/GeneratedValues.yaml.unanchored --version 0.2.17-rc39']' returned non-zero exit status 1.
version.BuildInfo{Version:"v3.5.1", GitCommit:"32c22239423b3b4ba6706d450bd044baffdcf9e6", GitTreeState:"clean", GoVersion:"go1.15.7"}
NAME        NAMESPACE        REVISION        UPDATED                                        STATUS          CHART                                   APP VERSION
dev         default          1               2021-08-04 11:17:06.603480028 +0000 UTC        deployed        cross-support-job-3p-0.2.17-rc39        19.02.1   
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Traceback (most recent call last):
  File "/usr/local/bin/onenv", line 104, in <module>
    main()
  File "/usr/local/bin/onenv", line 98, in main
    module.main()
  File "/usr/local/lib/one_env_engine/scripts/onenv_up.py", line 243, in main
    gui_pkg_verification=up_args.gui_pkg_verification
  File "/usr/local/lib/one_env_engine/scripts/onenv_up.py", line 55, in deploy_env
    local_chart_path, debug, dry_run)
  File "/usr/local/lib/one_env_engine/scripts/utils/deployment/scenario_runner.py", line 161, in run_scenario
    stderr=subprocess.STDOUT)
  File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/bin/bash', '-c', '/yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-12.05.13/scenarios/scenario-1oz-2op/ScenarioValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-12.05.13/scenarios/scenario-1oz-2op/ScenarioValues.yaml.unanchored ; /yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-12.05.13/scenarios/scenario-1oz-2op/GeneratedValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-12.05.13/scenarios/scenario-1oz-2op/GeneratedValues.yaml.unanchored ;  helm repo update; helm install dev onedata/cross-support-job-3p --namespace default -f /home/bamboo/.one-env/deployments/2021.08.04-12.05.13/scenarios/scenario-1oz-2op/ScenarioValues.yaml.unanchored -f /home/bamboo/.one-env/deployments/2021.08.04-12.05.13/scenarios/scenario-1oz-2op/GeneratedValues.yaml.unanchored --version 0.2.17-rc39']' returned non-zero exit status 1.
make: *** [Makefile:88: test_gui_pkg] Error 1
cp: cannot stat 'onedata/one_env/sources_info.yaml': No such file or directory
mv: cannot stat 'onedata/tests/gui/logs/gui_report/images.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  4658  100  4658    0     0  37264      0 --:--:-- --:--:-- --:--:-- 36968
Error: unknown flag: --purge
Error response from daemon: Cannot kill container: 8179e55010c9: Container 8179e55010c98a2d2d507ca2c99885dc205d50da6760d558e6abe7d6df06fbdf is not running
Error response from daemon: Cannot kill container: 10fe3f698a16: No such container: 10fe3f698a16
Error: No such container: 10fe3f698a16
Error response from daemon: Cannot kill container: 30ad946bdd35: No such container: 30ad946bdd35
Error: No such container: 30ad946bdd35
Error response from daemon: Cannot kill container: bb47b16b085e: No such container: bb47b16b085e
Error: No such container: bb47b16b085e
Error response from daemon: Cannot kill container: bff0fd31c0e2: No such container: bff0fd31c0e2
Error: No such container: bff0fd31c0e2
Error response from daemon: Cannot kill container: a6c100b496f3: Container a6c100b496f30bddddb58cab50b356c49bf38cd4710f52f3536effa84561cfcf is not running
Error response from daemon: Cannot kill container: 81dbeaa22419: No such container: 81dbeaa22419
Error: No such container: 81dbeaa22419
Error response from daemon: Cannot kill container: 09801632d770: No such container: 09801632d770
Error: No such container: 09801632d770
Error response from daemon: remove 1abcb77c03fb02c375c6b1f9729698e58412eea6e78590a96c9359d2dd7dfbf6: volume is in use - [8af5faa83b9a970f6c4d45dd0c5316e3f999230c2a48338df18d4a80a7750ca3]
Error response from daemon: remove 3dae516f1ad52a660401e84a3b1ebec2260d53beb60f084ccaa81e2e20dc2cbc: volume is in use - [ddeb4e0a5b6ac25c4c82b1f0d7dcb1f1be191b2687d3524ef9b78f54e651d20b]
Error response from daemon: remove 900e12fef499cf0c88d5639b88bf622b7e785990bad38b5433c7f8b930372ee0: volume is in use - [22f4f081eb8e0511f23738b61640d1e1a017f8206fe5be42238b41438d635558]
Error response from daemon: remove cbf0e48e5bb207a924c5613ea40fb2340a9ab7ca2dee11efb717226b8b5d63b6: volume is in use - [ddeb4e0a5b6ac25c4c82b1f0d7dcb1f1be191b2687d3524ef9b78f54e651d20b]
Error response from daemon: remove ccc1d91aa0038401f339a896453d32a1eddbb1e933ff2aeb4742189ae9c54bd1: volume is in use - [8af5faa83b9a970f6c4d45dd0c5316e3f999230c2a48338df18d4a80a7750ca3]
Error response from daemon: remove ea496528afa6a811aa387f0d2baf69f8b8a4081f9a0c505773771963ef935539: volume is in use - [cbe8c3fba3d16d800aadab16ba44f3d0dfc187362a7e3a76fb5a7e52cb588cb8]