🚨 Ansible Error: '... is not a valid attribute for a Task' — Cause, Fix, and Troubleshooting Guide

Overview

Every task, play, and block accepts a fixed set of keywords (name, when, loop, become, register, etc.). If Ansible finds a key at that level that is not a recognized keyword — almost always because module parameters were indented one level too shallow, or a keyword is misspelled — it refuses to load the playbook:

ERROR! 'state' is not a valid attribute for a Task

The error appears to be in '/etc/ansible/playbooks/site.yml': line 12, column 7

The offending key (state, path, src, mode, etc.) is usually a module parameter that ended up as a task attribute.

Symptoms

• The play fails to parse; no host is contacted.
• The error points at a real line and a key that belongs to a module, not a task.
• It appeared right after editing indentation or adding a parameter.

ansible-playbook -i inventory.ini site.yml --syntax-check

ERROR! 'mode' is not a valid attribute for a Task

Common Root Causes

1. Module parameters indented at the task level

The module name and its parameters must be nested under the module key. Flattening them makes state:/path: look like task keywords.

2. Misspelled task keyword

whenn:, regsiter:, notifiy: — a typo Ansible does not recognize.

3. A module parameter used without the module

Writing path: and state: with no module key at all.

4. loop/with_* or become misplaced

Placing a valid keyword under the module dict, or a module arg above it.

How to diagnose

Run a syntax check to get the exact line and column:

ansible-playbook site.yml --syntax-check

Inspect the indentation of the flagged task — module args should sit two spaces deeper than the module name:

sed -n '8,16p' site.yml | cat -A | head

Fixes

Nest module parameters under the module

Wrong (parameters at task level):

- name: Create directory
  ansible.builtin.file:
  path: /opt/app          # WRONG: indented at task level
  state: directory

Right:

- name: Create directory
  ansible.builtin.file:
    path: /opt/app         # nested under the module
    state: directory
    mode: "0755"

Fix a misspelled keyword

- name: Restart nginx
  ansible.builtin.service:
    name: nginx
    state: restarted
  when: reload_needed        # not "whenn"

Keep task keywords at the task level

- name: Install packages
  ansible.builtin.apt:
    name: "{{ item }}"
    state: present
  loop:                      # loop is a task keyword, not a module arg
    - nginx
    - curl

What to watch out for

• YAML indentation is the usual culprit — two spaces per level, no tabs. --syntax-check catches this before a real run.
• The same error says for a Play when a task-level keyword (like tasks: siblings) is misplaced at the play level.
• Editors that mix tabs and spaces produce this constantly; enable “show whitespace” or run yamllint.

Related

• Ansible Error: ‘Syntax Error while loading YAML’
• Ansible Error: ‘unsupported parameters for module’
• Ansible Error: ‘The conditional check failed’