Internal Error with Ansible-Lint on VSCode + VSCodium

Ask Fedora
1

I receive an unspecified Internal Error on both VSCode & VSCodium (I assume there’s no functional difference but I tried anyway). The exact error is Unexpected error code 1 from execution of: ansible-playbook --syntax-check -vv deploy_basevm.yamlansible-lintinternal-error. I do not receive the same when manually running ansible-playbook --syntax-check from the cli, just complaints about placeholder hostnames. Any idea what I can check? It’s a bit annoying to error on the first line and stop checking the file.

Python 3.14.2 according to the bottom right of VSCode, Ansible 2.18.2, VSCode Version: 1.109.0.

Playbook in entirety.

- name: Deploy new VM
  hosts: "{CHANGEME}"
  tasks:
# Look into API for Xen Orchestra to deploy VM.
# API call to Dashboard to set fixed IP
    - name: Set hostname of VM to something meaningful
      ansible.builtin.hostname:
        name: "{CHANGEME}"
        use: systemd
      become: true

    - name: Set IPv6 IID token
      ansible.builtin.shell:
        nmcli con mod enX0 ipv6.token ::"{CHANGEME}"
      become: true

    - name: Get IPv6 token
      ansible.builtin.shell:
        nmcli con show enX0 | grep ipv6.token
      register: ipv6_token_output

    - name: Print IPv6 token
      ansible.builtin.debug:
        msg: "{{ ipv6_token_output.stdout }}"

    - name: Set timezone
      community.general.timezone:
        name: America/New_York
      become: true

    - name: Update all packages
      ansible.builtin.dnf:
        name: "*"
        state: latest
      become: true

  vars_files: vault.yaml

# reboot the darn thing afterward and make sure we can test to the new v4 and v6 address.
# update BIND afterward with same playbook
2

Found some hints on the ansible forums. It seems that my vault being referenced while the system is unable to decrypt it causes the problem. I’ll have to have ansible-lint try to ignore the error or determine another way to reference secrets that doesn’t cause the problems.