edit 1: I forgot to mention this doesn't seem to happen on the initial run. But subsequent runs with pending changes will hit this.
edit 2: Pinning to v4.23.0 instead of main is a workaround.
Error
Message
{
"msg": "The 'file' lookup had an issue accessing the file '/etc/datadog-agent/install.json'. file not found, use -vvvvv to see paths searched",
"_ansible_no_log": false
}
Summary
The file exists, and the previous step confirms it exists. Then the task attempts to read the file and fails to find the file.
I believe this is because the
lookup
command occurs on the local computer, not on the remote computer.This step is also a new addition from three days ago: https://github.com/DataDog/ansible-datadog/pull/572/files
edit 1: I forgot to mention this doesn't seem to happen on the initial run. But subsequent runs with pending changes will hit this.
edit 2: Pinning to
v4.23.0
instead ofmain
is a workaround.Error
Message
Task
Parse install.json file if it exists
https://github.com/DataDog/ansible-datadog/blob/main/tasks/_agent-linux-macos-shared.yml#L106-L109Previous step of checking if file exists
Facts