Description of problem:

When the async task to run software deployment scripts times out, the subsequent task to dump stderr fails with the "The task includes an option with an undefined variable." message.
The output is cosmetic but it's better we avoid the error unrelated to the root cause.

~~~
2022-01-12 12:47:02,503 p=234567 u=mistral n=ansible | TASK [Run async deployment ControllerDeployment] *************************
...
2022-01-12 13:18:54,173 p=234567 u=mistral n=ansible | fatal: [controller-0]: FAILED! => {"changed": false, "msg": "async task did not complete within the requested time - 1800s"}
2022-01-12 13:18:54,173 p=234567 u=mistral n=ansible | ...ignoring
...
2022-01-12 13:18:58,959 p=234567 u=mistral n=ansible | TASK [Output for async deployment ControllerDeployment] ******************
...
2022-01-12 13:18:58,996 p=234567 u=mistral n=ansible | fatal: [controller-0]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stderr'\n\nThe error appears to be in '/var/lib/mistral/overcloud/deployments.yaml': line 193, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: \"Output for async deployment {{ item }}\"\n  ^ here\nWe could be wrong, but this one looks like it might be an issue with\nmissing quotes. Always quote template expression brackets when they\nstart a value. For instance:\n\n    with_items:\n      - {{ foo }}\n\nShould be written as:\n\n    with_items:\n      - \"{{ foo }}\"\n"}
...
2022-01-12 13:18:59,050 p=234567 u=mistral n=ansible | NO MORE HOSTS LEFT *************************************************************
2022-01-12 13:18:59,051 p=234567 u=mistral n=ansible | PLAY RECAP *********************************************************************
...  
2022-01-12 13:18:59,052 p=234567 u=mistral n=ansible | controller-0               : ok=67   changed=35   unreachable=0    failed=1    skipped=43   rescued=0    ignored=1   
...
~~~

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Implement a long sleep task (>1800 seconds) for ExtraConfigPre resource
2. Run deployment

Actual results:
Deployment fails and the undefined variable error is shown

Expected results:
Deployment fails and the undefined variable error is not shown

Additional info: