Opt/custom-venvs/.. is not a valid virtualenv in /var/lib/awx/venv”

AvatarPosted by

I received this error after adding some extra virtual environments in my AWX Kubernetes deployment. Hereby my troubleshooting steps and how I was able to resolve this (human)-error.

  1. Check if all your AWX / Tower task and web containers has the opt/custom-vens directory available. If the directories are not placed there, check your install script.
  2. The most common mistake is that the new custom venv directory is not (correctly) added to the global AWX settings. My fault was that I added the whole path including my custom venv to the global settings.

First we need to enable the new virtualenv path globally.
Change the URL, Username and Password and Custom Environment to your own variables.

After that we can assign that venv to our organization, job templates, projects and inventory.

Leave a Reply

Your email address will not be published. Required fields are marked *