[BUG]: Ansible Node 6 Deprecation Warning

[JtMotoX]

New issue checklist

• I searched for existing GitHub issues
• I read pipeline troubleshooting guide
• I checked how to collect logs

Extension name

Ansible

Extension version

0.230.2

Issue Description

The Ansible task is throwing a Node 6 deprecation warning on all of our pipelines.

##[warning]Task 'Ansible' version 0 (Ansible@0) is dependent on a Node version (6) that is end-of-life. Contact the extension owner for an updated version of the task. Task maintainers should review Node upgrade guidance: https://aka.ms/node-runner-guidance

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

RHEL9

Relevant log output

##[warning]Task 'Ansible' version 0 (Ansible@0) is dependent on a Node version (6) that is end-of-life. Contact the extension owner for an updated version of the task. Task maintainers should review Node upgrade guidance: https://aka.ms/node-runner-guidance

[PhilipsonJoseph]

Hi @JtMotoX May i know your self hosted agent version

[JtMotoX]

@PhilipsonJoseph 3.248.0

[PhilipsonJoseph]

Hi @JtMotoX We could see Ansible task have a support for Node 10. Could you check the node version installed on your agent machine. If it is Node 6 can you try to update the node version and test it again

[JtMotoX]

Hello @PhilipsonJoseph we don't install node on our machines. The modules use the node that is bundled with the agent. Each agent version ships with a set of node versions. The version we are using ships with v6, v10, v16, v20. It is up to the module to pick which node version to use; we have no control over this.

$ which node
/usr/bin/which: no node in ...

$ sudo find . -name node -type f | grep -v overlay2 | while read -r node; do printf '%s -> %s\n' $node $($node --version); done
./home/buildagent/agent/externals.3.246.0/node/bin/node -> v6.17.1
./home/buildagent/agent/externals.3.246.0/node20_1/bin/node -> v20.17.0
./home/buildagent/agent/externals.3.246.0/node16/bin/node -> v16.20.2
./home/buildagent/agent/externals.3.246.0/node10/bin/node -> v10.24.1
./home/buildagent/agent/externals.3.248.0/node16/bin/node -> v16.20.2
./home/buildagent/agent/externals.3.248.0/node20_1/bin/node -> v20.17.0
./home/buildagent/agent/externals.3.248.0/node/bin/node -> v6.17.1
./home/buildagent/agent/externals.3.248.0/node10/bin/node -> v10.24.1
./data/agent/_tool/node/14.21.3/x64/bin/node -> v14.21.3
./data/agent/_tool/node/18.20.4/x64/bin/node -> v18.20.4
./data/agent/_tool/node/20.18.0/x64/bin/node -> v20.18.0
./data/agent/_tool/node/12.22.12/x64/bin/node -> v12.22.12
./data/agent/_tool/node/10.24.1/x64/bin/node -> v10.24.1
./data/agent/_update/externals/node16/bin/node -> v16.20.2
./data/agent/_update/externals/node20_1/bin/node -> v20.17.0
./data/agent/_update/externals/node/bin/node -> v6.17.1
./data/agent/_update/externals/node10/bin/node -> v10.24.1

[PhilipsonJoseph]

@JtMotoX Can you share us the debug log of the task ?

[JtMotoX]

Here is what I am seeing:

==============================================================================
Task         : Ansible
Description  : This task executes an Ansible playbook using a specified inventory via command line interface
Version      : 0.230.2
Author       : Microsoft Corporation
Help         : [More Information](https://go.microsoft.com/fwlink/?linkid=853835)
==============================================================================
##[debug]Using node path: /vsts/home/buildagent/agent/externals/node/bin/node
. . .

The binary that the extension is using is v6:

$ /vsts/home/buildagent/agent/externals/node/bin/node --version
v6.17.1

Again, this version of node is bundled with the agent. We did not install this. We simply provisioned a VM and deployed the Azure DevOps Agent.

We saw this issue with other extensions we were using and the vendor provided an update to their extension which fixed the issue.

[JtMotoX]

Here are some links I found that might be helpful:

https://github.com/microsoft/azure-pipelines-tasks/blob/master/docs/migrateNode16.md

https://johnnyreilly.com/azure-pipelines-custom-pipelines-task-extension-node-16