Ansible Meta Data warns Ansible Lint missing

Sanity check

• I certify that the redhat.ansible extension is in use and the language of the document in this bug report shows up as Ansible

Summary

“Ansible Meta data” warns that Ansible Lint is missing, but it is installed and working. I guess the extension is not finding the “python3” executable, it only tries “python” which an Ubuntu does not provide out of the box.

Extension version

v0.12.30

VS Code version

1.70.2

Ansible Version

$ ansible --version
ansible [core 2.13.2]
  config file = /home/xx/projects/ansible/ansible.cfg
  configured module search path = ['/home/xx/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/xx/.local/lib/python3.10/site-packages/ansible
  ansible collection location = /home/xx/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/xx/.local/bin/ansible
  python version = 3.10.4 (main, Apr  2 2022, 09:04:19) [GCC 11.2.0]
  jinja version = 3.0.3
  libyaml = True

OS / Environment

Windows 11 Enterprise -> VS Code -> WSL Ubuntu 22.04 LTS

$ ansible-lint --version ansible-lint 6.0.2 using ansible 2.13.2

$ ansible --version | grep “python version” python version = 3.10.4 (main, Apr 2 2022, 09:04:19) [GCC 11.2.0]

Relevant log output

Path for lint:  /home/xx/.local/bin/ansible-lint
Validating using ansible-lint
cmd 'python --version' was not executed with the following error: ' Error: Command failed: python --version
/bin/sh: 1: python: not found

cmd 'ansible-lint --version' has the following error: WARNING: PATH altered to include /usr/bin

[Info  - 7:30:08 PM] [ansible-lint] WARNING: PATH altered to include /usr/bin
WARNING  Loading custom .yamllint config file, this extends our internal yamllint config.

[ssbarnea]

Lets see what @priyamsahoo can say about it, maybe we failed to release ALS. He had few days of vacation but should be back next week. I will reopen the bug so we do not forget about it.

[max06]

Closing as we already released a fix for few days ago.

Hey @ssbarnea, when do you expect this fix to arrive? As of v0.13.68 (pre-release) this issue still persists.