Can't find PythonVersion on self hosted ubuntu image about azure-pipelines-tool-lib HOT 7 CLOSED

Ok, so to be precise, the issue here is that AGENT_TOOLSDIRECTORY is set to one thing, but Agent.ToolsDirectory is getting set to something else?

In theory that shouldn't happen. To help diagnose - in your pipeline, before your usePythonVersion step, could you add a script to echo AGENT_TOOLSDIRECTORY? That should help us determine where exactly this issue is coming from. I believe that .../_work/tools is the default tools directory when none is found so my guess is that its being lost before then

from azure-pipelines-tool-lib.

Closing due to inactivity. Please reopen with additional information.

from azure-pipelines-tool-lib.

When I do ls im getting these fiiles instead.

/var/lib/waagent/custom-script/download/1/agent/_work/_tool
helm
kubectl

but doing it on the server is pointing to the right folders where I can see python, ruby and pypy

from azure-pipelines-tool-lib.

Not all python versions are available on all images. If you go to this link, click on the Available Software for the Image you are using, it will list all the software versions on your image.

For example: if you are running Ubuntu 16.04 or Ubuntu 18.04 the only 3.6.x version of python available to you is 3.6.9

https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops#software

from azure-pipelines-tool-lib.

Hi @dave-ops we are talking about self hosted. and definitely I can confirm that 3.7.* and 3.8.* are all in toolscache folder.

from azure-pipelines-tool-lib.

Hi. If your agent is started as a service, it will not be aware of the AGENT_TOOLSDIRECTORY environment variable you set. https://github.com/microsoft/azure-pipelines-agent/blob/master/docs/start/nixsvc.md#setting-the-environment

Adding it to the .env file should solve your issue.

from azure-pipelines-tool-lib.

Hi. If your agent is started as a service, it will not be aware of the AGENT_TOOLSDIRECTORY environment variable you set. https://github.com/microsoft/azure-pipelines-agent/blob/master/docs/start/nixsvc.md#setting-the-environment

Adding it to the .env file should solve your issue.

Hi, from the pipeline log, I find that the env is already be recognized. But I still meet this issue. The log is below.

##[debug]versionSpec=3.7
##[debug]addToPath=true
##[debug]architecture=x64
##[debug]Semantic version spec of 3.7 is 3.7
##[debug]isExplicit: null
##[debug]explicit? false
##[debug]Agent.Version=2.165.2
##[debug]Agent.ToolsDirectory=/home/vmasuser/myagent/_work/_tool
##[debug]isExplicit: 3.7.7
##[debug]explicit? true
##[debug]evaluating 0 versions
##[debug]match not found
##[debug]Agent.Version=2.165.2
##[debug]Agent.ToolsDirectory=/home/vmasuser/myagent/_work/_tool
##[debug]isExplicit: 3.7.7
##[debug]explicit? true
##[debug]Agent.Version=2.165.2
##[debug]Agent.ToolsDirectory=/home/vmasuser/myagent/_work/_tool
##[debug]isExplicit: 3.7.7
##[debug]explicit? true
##[debug]Agent.ToolsDirectory=/home/vmasuser/myagent/_work/_tool
##[debug]task result: Failed
##[error]Version spec 3.7 for architecture x64 did not match any version in Agent.ToolsDirectory.
Versions in /home/vmasuser/myagent/_work/_tool:

If this is a Microsoft-hosted agent, check that this image supports side-by-side versions of Python at https://aka.ms/hosted-agent-software.
If this is a self-hosted agent, see how to configure side-by-side Python versions at https://go.microsoft.com/fwlink/?linkid=871498.

from azure-pipelines-tool-lib.