GUI acceptance tests using environment deployed from packages.

Build: #1644 failed

Job: Onezone data discovery failed

Job result summary

Completed
Duration
10 minutes
Revision
8ef115ec7d87053dbcde4b51692c10279a72317d
Total tests
32
Fixed in
#1717 (Changes by Jakub Liput and Tomek Krzyzak)
No failed test found. A possible compilation error occurred.

Tests

  • 32 tests in total
  • 32 tests were quarantined / skipped
  • 58 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4658  100  4658    0     0  20794      0 --:--:-- --:--:-- --:--:-- 20702
Error: unknown flag: --purge
Error: No such object: fd18dbbbb1b8
Error: No such object: fd18dbbbb1b8
Error: No such object: a7a65cdb56d9
Error: No such object: a7a65cdb56d9
Error: No such object: cbd1e31116c9
Error: No such object: cbd1e31116c9
Error: No such object: 84862d2bc99e
Error: No such object: 84862d2bc99e
Error: No such object: aeb3bae1dabe
Error: No such object: aeb3bae1dabe
Error: No such object: a894b10df02e
Error: No such object: a894b10df02e
Error response from daemon: Cannot kill container: a5fba19371c0: No such container: a5fba19371c0
Error: No such container: a5fba19371c0
Error response from daemon: Cannot kill container: 18123451c5dd: Container 18123451c5dd427e0f6216e318543d3e9d103be5c7941c2e1ef2961a443c1975 is not running
Error response from daemon: Cannot kill container: d2068cb6a0ad: Container d2068cb6a0adff836a09dfc025a0f9695afd81aa99b0a2707543015e10494651 is not running
Error response from daemon: Cannot kill container: 822f991708d4: No such container: 822f991708d4
Error: No such container: 822f991708d4
Error response from daemon: Cannot kill container: d0849b8be738: Container d0849b8be738d90e9401998cf7e9f7e16c5f18f3c0c8db6971bd56157a8c2817 is not running
Error response from daemon: Cannot kill container: fd18dbbbb1b8: No such container: fd18dbbbb1b8
Error: No such container: fd18dbbbb1b8
Error response from daemon: Cannot kill container: 181e2fe21cf4: No such container: 181e2fe21cf4
Error: No such container: 181e2fe21cf4
Error response from daemon: Cannot kill container: a7a65cdb56d9: No such container: a7a65cdb56d9
Error: No such container: a7a65cdb56d9
Error response from daemon: Cannot kill container: acea6f2a9877: Container acea6f2a98779b55ee12c94bf789889b7c937ee9611ce27544a0828ad2c43959 is not running
Error response from daemon: Cannot kill container: cbd1e31116c9: No such container: cbd1e31116c9
Error: No such container: cbd1e31116c9
Error response from daemon: Cannot kill container: 84862d2bc99e: No such container: 84862d2bc99e
Error: No such container: 84862d2bc99e
Error response from daemon: Cannot kill container: aeb3bae1dabe: No such container: aeb3bae1dabe
Error: No such container: aeb3bae1dabe
Error response from daemon: Cannot kill container: a894b10df02e: No such container: a894b10df02e
Error: No such container: a894b10df02e
Error response from daemon: remove 3a4e31d713518b9905a44a47cfc2ead174fe4d8e2568a886fa98b742ff4f1db2: volume is in use - [84e6c1528a4dc530d18c69354f74373d8f2085dce0aa002cee19e95178195ced]
Error response from daemon: remove 477f16d364f19bb31eeda21d6d512705d4faa34dbb7048d3e2ddc5674f6ee456: volume is in use - [6dbc2bdcf40901606fa2919d5802d8a45a9c9239b364de1c842d41316765fd73]
Error response from daemon: remove 861d7965b787b889959777ac0ba6c0799ffa108081abf14bf5dacc566ab1e09f: volume is in use - [84e6c1528a4dc530d18c69354f74373d8f2085dce0aa002cee19e95178195ced]
Error response from daemon: remove add3b6f3a7552980c0ec5dd2926b015a25b279316eaf0e5b49c8bb332aed6c47: volume is in use - [17310d26f5e993538ad68766df837913e9c41930e18a257b79188019d6355dde]
Error response from daemon: remove bbf0eca9960ff40d70c8c76425120284cc6cc0cc1d5553a60d64b2ba8559ecb4: volume is in use - [7499dec759b77bec8029793b2802af717680a1f25517cb830abb170845ef79ce]
Error response from daemon: remove ea7e292c56621a27415847e9eaff7e51435b20088be6c72d686ff5499880f730: volume is in use - [17310d26f5e993538ad68766df837913e9c41930e18a257b79188019d6355dde]
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-CODDT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODDT/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-CODDT/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-CODDT/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-CODDT/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:16:13.479360275 +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
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: 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:16:13.479360275 +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:16:13.479360275 +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.06.02/scenarios/scenario-1oz-1op/ScenarioValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-12.06.02/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored ; /yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-12.06.02/scenarios/scenario-1oz-1op/GeneratedValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-12.06.02/scenarios/scenario-1oz-1op/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.06.02/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored -f /home/bamboo/.one-env/deployments/2021.08.04-12.06.02/scenarios/scenario-1oz-1op/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:16:13.479360275 +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.06.19/scenarios/scenario-1oz-1op/ScenarioValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-12.06.19/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored ; /yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-12.06.19/scenarios/scenario-1oz-1op/GeneratedValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-12.06.19/scenarios/scenario-1oz-1op/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.06.19/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored -f /home/bamboo/.one-env/deployments/2021.08.04-12.06.19/scenarios/scenario-1oz-1op/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:16:13.479360275 +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.06.37/scenarios/scenario-1oz-1op/ScenarioValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-12.06.37/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored ; /yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-12.06.37/scenarios/scenario-1oz-1op/GeneratedValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-12.06.37/scenarios/scenario-1oz-1op/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.06.37/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored -f /home/bamboo/.one-env/deployments/2021.08.04-12.06.37/scenarios/scenario-1oz-1op/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
100  4658  100  4658    0     0  37869      0 --:--:-- --:--:-- --:--:-- 37869
Error: unknown flag: --purge
Error response from daemon: Cannot kill container: b96c49bcb6a3: Container b96c49bcb6a38168efb2cf1e466cb0b283fa418f66a12de691327c766274d7f2 is not running
Error response from daemon: Cannot kill container: 0f1ee14b766a: Container 0f1ee14b766ab80b93d9e6e39c93fa3e7e44120a01ab4f4438a5f78a1b59b8b4 is not running
Error response from daemon: Cannot kill container: bffa3bb5c5e3: No such container: bffa3bb5c5e3
Error: No such container: bffa3bb5c5e3
Error response from daemon: Cannot kill container: 0d9b7253875d: No such container: 0d9b7253875d
Error: No such container: 0d9b7253875d
Error response from daemon: Cannot kill container: 16055e30dd8f: No such container: 16055e30dd8f
Error: No such container: 16055e30dd8f
Error response from daemon: Cannot kill container: 6dbc2bdcf409: No such container: 6dbc2bdcf409
Error: No such container: 6dbc2bdcf409
Error response from daemon: Cannot kill container: 7508929e829f: No such container: 7508929e829f
Error: No such container: 7508929e829f
Error response from daemon: remove 1ca129a240f022fb8d37d4c68a17c0db89986cea377bcce78fda68bf659fd8c0: volume is in use - [74e0358f4e66c98ce65336f0cb83df9bc512f185af502c49307d347919d957fc]
Error response from daemon: remove 8c305cad764af503f9d5fa58e533d26a64f6e2e98f1ac4307b38504732556468: volume is in use - [70ca8586fd5d98a95b521175e259d9c394b107ddd9e3434b90a748462843a430]
Error response from daemon: remove 361f5c8af2b2ab8852b6ecac69983ff912904f87a9108f214238cfb7aeb83b74: volume is in use - [74e0358f4e66c98ce65336f0cb83df9bc512f185af502c49307d347919d957fc]
Error response from daemon: remove 945c06c1b4e8c4a1c73102255b3f044353372fd01a0c9a762851e713d1bda7ab: volume is in use - [7c95e1d0b324cbe821dea65f4bb6c5bae1d37d6c2dee77f300efcbf3834e965c]
Error response from daemon: remove 82681572c5b06cbe6c056b356d75fc777dd43e41fbd2e261f16a8e8ccf38a68f: volume is in use - [27e52ee33d1c83dc55001c288b7c9e3c86159ec2af8964f113eab86a1166b4d1]
Error response from daemon: remove ba94ded7f37a295727196ecf739ca2dfdde4a50de8ce3faa80ec387828d2c9d0: volume is in use - [27e52ee33d1c83dc55001c288b7c9e3c86159ec2af8964f113eab86a1166b4d1]
Error response from daemon: remove de4cb264f888273fae2158adbb8c4de9740c8342024021df5bf4c1cb9f81b8ba: volume is in use - [41a5dc56f723914979c07af2d0d4d4d6fe2e8756ad8ed6db6682d2cc527a394e]
Error response from daemon: remove e712df048fec4b0914f397072f0e2f78013cdd0b4c889268e718ecfdf242067b: volume is in use - [70ca8586fd5d98a95b521175e259d9c394b107ddd9e3434b90a748462843a430]