-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
2.3, 2.4
-
None
-
False
-
-
False
1. What is the nature and description of the request?
The CUSTOM_VENV_PATHS is still present in the Automation Controller API:
"DEFAULT_EXECUTION_ENVIRONMENT": null, "CUSTOM_VENV_PATHS": [], "INSIGHTS_TRACKING_STATE": false,
But, this parameter is not visible from Controller UI. The virtual environments were used in Ansible Automation Platform 1.2 and Ansible Tower 3.X but, they were replaced by the Execution Environments since Ansible Automation Platform 2.
2. Why does the customer need this? (List the business requirements here)
We have seen some cases which the customers were getting some issues, due to the CUSTOM_VENV_PATHS, as the following:
rest_framework.exceptions.ValidationError: [ErrorDetail(string='/var/lib/awx/venv/ansible is not a valid path choice.', code='path_error')] 2024-04-17 06:15:25,158 WARNING [6d0ce50cd2c54c06abb8aaad429843d0] awx.conf.settings The current value "['/var/lib/awx/venv/ansible', '/var/lib/awx/venv/ansible2100_core', '/var/lib/awx/venv/ansible2915_core', '/var/lib/awx/venv/ansible_admin', '/var/lib/awx/venv/ansible_python3']" for setting "CUSTOM_VENV_PATHS" is invalid.
This happens due to the parameter still contains values in the API:
"CUSTOM_VENV_PATHS": [ "/var/lib/awx/venv/ansible", "/var/lib/awx/venv/ansible2100_core", "/var/lib/awx/venv/ansible2915_core", "/var/lib/awx/venv/ansible_admin", "/var/lib/awx/venv/ansible_python3"
If this value is removed, we could avoid some issues/errors due to this.
