Why does my tasks file (under tasks/do_sth/do_sth.yaml) say "block is a required property"?

[blv-brunoneyra]

File looks like this:

- hosts: all
  become: true

  tasks:
    - name: Clean logs
      ansible.builtin.file:
        state: absent
        path: "/var/log/myproj.log"

and it says:

'block' is a required property [schema[tasks]]

[fxlv]

I'm not an expert on this, and, perhaps, your case is/was different, but I also hit the similar/same issue today and this was one of very few google hits for me, hence I will make a comment on how I solved it.

I experienced warning from ansible-lint:

schema[tasks]: 'block' is a required property

Looking at ansible-lint docs I learned that ansible-lint considers directory structure to figure out what the purpose of the file is.

I had my playbook as ansible_dir\tasks\stuff.yml which the linter complained about as it assumed it is just a list of tasks, but for me, it was a playbook.
Once I changed directory structure to be ansible_dir\playbooks\stuff.yml the linter was happy and so was I.

I learned that while Ansible itself is pretty relaxed and does not force you to use one specific directory/file layout, without such layout the linter would have hard time figuring out what is what.

[pythoninthegrass]

Thanks for taking the time to write this out! Silly that directory structure can't be customized/ignored with ansible-lint, but for my purposes, this workaround did the trick 🙏

[dcunited001]

jenkies ... i think it is a "blocking"

[x] somewhat confused now
[ ] move files from tasks to playbooks

please ignore this, but ansible lsp is crash big crash.

my stapler. no logs

[VGerris]

I encountered a similar issue :
'role' is a required property

I had a playbook.yaml file in the root dir and a tasks subdir.
When creating a playbooks dir and moving it there, the linter does not complain.
Feels like a bug to me, where the linter is unable to see it is a playbook, even when it has a roles directive.
Isn't that a bug ?