GUI acceptance tests using environment deployed from packages.
Build: #1644 failed
Job: Chrome oneprovider ACL files multi failed
Job result summary
- Completed
- Duration
- 3 minutes
- Revision
-
8ef115ec7d87053dbcde4b51692c10279a72317d
- Total tests
- 26
- Fixed in
- #1648 (Changes by Bamboo Agent <bamboo@cloud.plgrid.pl>)
Configuration changes
Tests
- 26 tests in total
- 26 tests were quarantined / skipped
- 39 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 21232 0 --:--:-- --:--:-- --:--:-- 21269
Error from server (NotFound): pods "dev-onezone-ready-check-g6gxc" not found
Error response from daemon: Cannot kill container: 983e712e276c: Container 983e712e276cae36e11b18cb9edce0fcadda760e772c5a0cf5f7de2e1ab84828 is not running
Error response from daemon: Cannot kill container: 3116867c56cb: Container 3116867c56cbd6ba49e51b7ced1e02a2e5bf67943c52d9b6bfc71a433e0c582c is not running
Error response from daemon: Cannot kill container: c698118be163: Container c698118be16375fe53f2b5d427f9909c84338df5ffbe2f94afd33d1ccf08431a is not running
Error response from daemon: Cannot kill container: 946f9816fe8d: Container 946f9816fe8d07a91742580f3bdf1ce85b1f33a9efacc84a420d5765af7cb6c0 is not running
Error response from daemon: Cannot kill container: ed69e9831270: Container ed69e9831270669f2526b3c6e3bd47b63c1b78ffc7d6e0d1f013aa134368dde3 is not running
Error response from daemon: Cannot kill container: 4e81075dee90: Container 4e81075dee90d665b9079aab244da033e8bf47137937d6b91422ca7534226392 is not running
Error response from daemon: Cannot kill container: 7882c5256d91: Container 7882c5256d91df1504c3ccafdab670d9e667d34f9ba37c3be9906a1cc94fb38e is not running
Error response from daemon: remove 07b9acd2790113bda05d506e62ce96172791b7b4e57864ce5dd6876359b067c1: volume is in use - [7b66a2204d6539eeab4016e4fb998adb6d20cc1b22d24f238a6823aedf94d552]
Error response from daemon: remove 8e7b2032c7d26fac4bc6f00da277337c687b89567b1b76be18474a1c97a48171: volume is in use - [3849441f230db548ef32b452f1faae705ffec2b24205983dfa04851bc478e123]
Error response from daemon: remove 516f1481f5ce7b39192227ac9a31adae90df9becb17b8dbeefd4852d3a172dda: volume is in use - [3849441f230db548ef32b452f1faae705ffec2b24205983dfa04851bc478e123]
Error response from daemon: remove a40cb169801a780e07652fbe19f6974dbe9923cd5bee48093439333504ce9aeb: volume is in use - [de40fde101d5d2f83a39d8852f7ba313299d27329730df6837cc0cd6b73735bb]
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'...
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:29:48.197494853 +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 create /home/bamboo/.helm: mkdir /home/bamboo/.helm: permission denied
Error: Could not create /home/bamboo/.helm: mkdir /home/bamboo/.helm: permission denied
Error: Could not create /home/bamboo/.helm: mkdir /home/bamboo/.helm: permission denied
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:29:48.197494853 +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:29:48.197494853 +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-11.55.49/scenarios/scenario-1oz-1op/ScenarioValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-11.55.49/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored ; /yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-11.55.49/scenarios/scenario-1oz-1op/GeneratedValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-11.55.49/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-11.55.49/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored -f /home/bamboo/.one-env/deployments/2021.08.04-11.55.49/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:29:48.197494853 +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-11.56.01/scenarios/scenario-1oz-1op/ScenarioValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-11.56.01/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored ; /yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-11.56.01/scenarios/scenario-1oz-1op/GeneratedValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-11.56.01/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-11.56.01/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored -f /home/bamboo/.one-env/deployments/2021.08.04-11.56.01/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:29:48.197494853 +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-11.56.12/scenarios/scenario-1oz-1op/ScenarioValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-11.56.12/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored ; /yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-11.56.12/scenarios/scenario-1oz-1op/GeneratedValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-11.56.12/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-11.56.12/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored -f /home/bamboo/.one-env/deployments/2021.08.04-11.56.12/scenarios/scenario-1oz-1op/GeneratedValues.yaml.unanchored --version 0.2.17-rc39']' returned non-zero exit status 1.
make: *** [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 21327 0 --:--:-- --:--:-- --:--:-- 21366
Error response from daemon: Cannot kill container: 4de895f90b57: Container 4de895f90b5799e682deca72cad3f20302906bec0acadd46f0f211fc3c5197a1 is not running
Error response from daemon: Cannot kill container: 93c407f432c7: Container 93c407f432c7dbc28bd4f25de4d9fb1209c3f3a903a8e65404d8a6ce7bf1bbed is not running
Error response from daemon: Cannot kill container: 306db80727ed: No such container: 306db80727ed
Error: No such container: 306db80727ed
Error response from daemon: Cannot kill container: ded5994ce98b: No such container: ded5994ce98b
Error: No such container: ded5994ce98b
Error response from daemon: Cannot kill container: de40fde101d5: No such container: de40fde101d5
Error: No such container: de40fde101d5
Error response from daemon: Cannot kill container: 2f6bf4d6bbda: No such container: 2f6bf4d6bbda
Error: No such container: 2f6bf4d6bbda
Error response from daemon: Cannot kill container: d5370e19cf3e: Container d5370e19cf3e7b821550a750b537f514f08d5aba7c0515abb48a35bac24a4fc8 is not running
Error response from daemon: Cannot kill container: e918acdd56ba: Container e918acdd56bab96d25d2feaab00bebbea0a969447d9acb3432c187a859d31716 is not running
Error response from daemon: remove 5b6cbc30b1fdc741a8c31f13df3d0d0436a247c4a83f02461d63844122cf963c: volume is in use - [39612f7a6488e9867831b2a2f6673426761efd4353fb49e53e761158ed373c12]
Error response from daemon: remove 7fe0f8968595c8f60a3b20ae0dd7399e24461c1b244d39cfa5d2e2ef09aa6dac: volume is in use - [78318294d956eebf9f2bca2b39e0dd6a8512b6192834e8d40e7f0b9f6e0e884c]
Error response from daemon: remove ae8c6700514523b219f5c982c99cc1bd3b7f921223db207c503f67244a2f1419: volume is in use - [39612f7a6488e9867831b2a2f6673426761efd4353fb49e53e761158ed373c12]
Error response from daemon: remove c97e068e4ad037f73c41e60c62f48d6ea147f6b10c56857120802a51d2c42d89: volume is in use - [0806f504de914132db77e957639ab5458171759c2784a57d37966e4568414edf]
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 4658 100 4658 0 0 21232 0 --:--:-- --:--:-- --:--:-- 21269
Error from server (NotFound): pods "dev-onezone-ready-check-g6gxc" not found
Error response from daemon: Cannot kill container: 983e712e276c: Container 983e712e276cae36e11b18cb9edce0fcadda760e772c5a0cf5f7de2e1ab84828 is not running
Error response from daemon: Cannot kill container: 3116867c56cb: Container 3116867c56cbd6ba49e51b7ced1e02a2e5bf67943c52d9b6bfc71a433e0c582c is not running
Error response from daemon: Cannot kill container: c698118be163: Container c698118be16375fe53f2b5d427f9909c84338df5ffbe2f94afd33d1ccf08431a is not running
Error response from daemon: Cannot kill container: 946f9816fe8d: Container 946f9816fe8d07a91742580f3bdf1ce85b1f33a9efacc84a420d5765af7cb6c0 is not running
Error response from daemon: Cannot kill container: ed69e9831270: Container ed69e9831270669f2526b3c6e3bd47b63c1b78ffc7d6e0d1f013aa134368dde3 is not running
Error response from daemon: Cannot kill container: 4e81075dee90: Container 4e81075dee90d665b9079aab244da033e8bf47137937d6b91422ca7534226392 is not running
Error response from daemon: Cannot kill container: 7882c5256d91: Container 7882c5256d91df1504c3ccafdab670d9e667d34f9ba37c3be9906a1cc94fb38e is not running
Error response from daemon: remove 07b9acd2790113bda05d506e62ce96172791b7b4e57864ce5dd6876359b067c1: volume is in use - [7b66a2204d6539eeab4016e4fb998adb6d20cc1b22d24f238a6823aedf94d552]
Error response from daemon: remove 8e7b2032c7d26fac4bc6f00da277337c687b89567b1b76be18474a1c97a48171: volume is in use - [3849441f230db548ef32b452f1faae705ffec2b24205983dfa04851bc478e123]
Error response from daemon: remove 516f1481f5ce7b39192227ac9a31adae90df9becb17b8dbeefd4852d3a172dda: volume is in use - [3849441f230db548ef32b452f1faae705ffec2b24205983dfa04851bc478e123]
Error response from daemon: remove a40cb169801a780e07652fbe19f6974dbe9923cd5bee48093439333504ce9aeb: volume is in use - [de40fde101d5d2f83a39d8852f7ba313299d27329730df6837cc0cd6b73735bb]
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'...
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:29:48.197494853 +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 create /home/bamboo/.helm: mkdir /home/bamboo/.helm: permission denied
Error: Could not create /home/bamboo/.helm: mkdir /home/bamboo/.helm: permission denied
Error: Could not create /home/bamboo/.helm: mkdir /home/bamboo/.helm: permission denied
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:29:48.197494853 +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:29:48.197494853 +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-11.55.49/scenarios/scenario-1oz-1op/ScenarioValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-11.55.49/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored ; /yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-11.55.49/scenarios/scenario-1oz-1op/GeneratedValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-11.55.49/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-11.55.49/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored -f /home/bamboo/.one-env/deployments/2021.08.04-11.55.49/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:29:48.197494853 +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-11.56.01/scenarios/scenario-1oz-1op/ScenarioValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-11.56.01/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored ; /yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-11.56.01/scenarios/scenario-1oz-1op/GeneratedValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-11.56.01/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-11.56.01/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored -f /home/bamboo/.one-env/deployments/2021.08.04-11.56.01/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:29:48.197494853 +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-11.56.12/scenarios/scenario-1oz-1op/ScenarioValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-11.56.12/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored ; /yaml-anchors /home/bamboo/.one-env/deployments/2021.08.04-11.56.12/scenarios/scenario-1oz-1op/GeneratedValues.yaml > /home/bamboo/.one-env/deployments/2021.08.04-11.56.12/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-11.56.12/scenarios/scenario-1oz-1op/ScenarioValues.yaml.unanchored -f /home/bamboo/.one-env/deployments/2021.08.04-11.56.12/scenarios/scenario-1oz-1op/GeneratedValues.yaml.unanchored --version 0.2.17-rc39']' returned non-zero exit status 1.
make: *** [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 21327 0 --:--:-- --:--:-- --:--:-- 21366
Error response from daemon: Cannot kill container: 4de895f90b57: Container 4de895f90b5799e682deca72cad3f20302906bec0acadd46f0f211fc3c5197a1 is not running
Error response from daemon: Cannot kill container: 93c407f432c7: Container 93c407f432c7dbc28bd4f25de4d9fb1209c3f3a903a8e65404d8a6ce7bf1bbed is not running
Error response from daemon: Cannot kill container: 306db80727ed: No such container: 306db80727ed
Error: No such container: 306db80727ed
Error response from daemon: Cannot kill container: ded5994ce98b: No such container: ded5994ce98b
Error: No such container: ded5994ce98b
Error response from daemon: Cannot kill container: de40fde101d5: No such container: de40fde101d5
Error: No such container: de40fde101d5
Error response from daemon: Cannot kill container: 2f6bf4d6bbda: No such container: 2f6bf4d6bbda
Error: No such container: 2f6bf4d6bbda
Error response from daemon: Cannot kill container: d5370e19cf3e: Container d5370e19cf3e7b821550a750b537f514f08d5aba7c0515abb48a35bac24a4fc8 is not running
Error response from daemon: Cannot kill container: e918acdd56ba: Container e918acdd56bab96d25d2feaab00bebbea0a969447d9acb3432c187a859d31716 is not running
Error response from daemon: remove 5b6cbc30b1fdc741a8c31f13df3d0d0436a247c4a83f02461d63844122cf963c: volume is in use - [39612f7a6488e9867831b2a2f6673426761efd4353fb49e53e761158ed373c12]
Error response from daemon: remove 7fe0f8968595c8f60a3b20ae0dd7399e24461c1b244d39cfa5d2e2ef09aa6dac: volume is in use - [78318294d956eebf9f2bca2b39e0dd6a8512b6192834e8d40e7f0b9f6e0e884c]
Error response from daemon: remove ae8c6700514523b219f5c982c99cc1bd3b7f921223db207c503f67244a2f1419: volume is in use - [39612f7a6488e9867831b2a2f6673426761efd4353fb49e53e761158ed373c12]
Error response from daemon: remove c97e068e4ad037f73c41e60c62f48d6ea147f6b10c56857120802a51d2c42d89: volume is in use - [0806f504de914132db77e957639ab5458171759c2784a57d37966e4568414edf]