ansible_failed_task is undefined in the rescue section if an error is thrown from a loop task

[ghost]

Summary

Referencing:

• ansible_failed_task is referencing out of scope loop variables. #57399
• Ansible_failed_task is referencing (out of scope) default variables from included role #49942

This fix #73881 does not fix those above.

Issue Type

Bug Report

Component Name

block

Ansible Version

$ ansible --version
ansible 2.9.20
  config file = ansible.cfg
  configured module search path = [u'/home/ansible/ansible/modules']
  ansible python module location = /home/ansible/.local/lib/python2.7/site-packages/ansible
  executable location = /home/ansible/.local/bin/ansible
  python version = 2.7.12 (default, Mar  1 2021, 11:38:31) [GCC 5.4.0 20160609]

Configuration

$ ansible-config dump --only-changed

OS / Environment

Ubuntu 16.04.5 LTS (Xenial Xerus)

Steps to Reproduce

- hosts: localhost
  gather_facts: no
  vars:
    ansible_connection: local
    data:
      - name: a1
      - name: a2
      - name: a3

  tasks:
    - debug:
        msg: "{{ data }}"
    - name: Block START
      block:
      - name: LOOP TASK
        debug:
          msg: "The element is: {{ item.name }}"
        loop: "{{ data }}"
        failed_when: item.name is defined

      rescue:
        - name: print ansible_failed_task
          debug:
            var: ansible_failed_task

        - name: print ansible_failed_result
          debug:
            var: ansible_failed_result

Expected Results

ansible_failed_task is defined

Actual Results

PLAY [localhost] **********************************************************************************

TASK [debug] **************************************************************************************
Thursday 15 April 2021  20:10:07 +0000 (0:00:03.476)       0:00:03.476 ******** 
ok: [localhost] => {
    "msg": [
        {
            "name": "a1"
        }, 
        {
            "name": "a2"
        }, 
        {
            "name": "a3"
        }
    ]
}

TASK [LOOP TASK] **********************************************************************************
Thursday 15 April 2021  20:10:07 +0000 (0:00:00.037)       0:00:03.513 ******** 
failed: [localhost] (item={u'name': u'a1'}) => {
    "msg": "The element is: a1"
}
failed: [localhost] (item={u'name': u'a2'}) => {
    "msg": "The element is: a2"
}
failed: [localhost] (item={u'name': u'a3'}) => {
    "msg": "The element is: a3"
}
fatal: [localhost]: FAILED! => {"msg": "All items completed"}

TASK [print ansible_failed_task] ******************************************************************
Thursday 15 April 2021  20:10:07 +0000 (0:00:00.049)       0:00:03.563 ******** 
ok: [localhost] => {
    "ansible_failed_task": "VARIABLE IS NOT DEFINED!"
}

TASK [print ansible_failed_result] ****************************************************************
Thursday 15 April 2021  20:10:07 +0000 (0:00:00.034)       0:00:03.598 ******** 
ok: [localhost] => {
    "ansible_failed_result": {
        "changed": false, 
        "failed": true, 
        "msg": "All items completed", 
        "results": [
            {
                "ansible_loop_var": "item", 
                "changed": false, 
                "failed": true, 
                "failed_when_result": true, 
                "item": {
                    "name": "a1"
                }, 
                "msg": "The element is: a1"
            }, 
            {
                "ansible_loop_var": "item", 
                "changed": false, 
                "failed": true, 
                "failed_when_result": true, 
                "item": {
                    "name": "a2"
                }, 
                "msg": "The element is: a2"
            }, 
            {
                "ansible_loop_var": "item", 
                "changed": false, 
                "failed": true, 
                "failed_when_result": true, 
                "item": {
                    "name": "a3"
                }, 
                "msg": "The element is: a3"
            }
        ]
    }
}

Code of Conduct

I agree to follow the Ansible Code of Conduct

[sivel]

This was literally fixed minutes ago in #74290

[ghost]

Indeed. Just applied the patch and tested in few real world cases. Everything is working now. Thanks. Closing this one.