Machine agent install seems to look for db-agent path

[pk-z1]

Hello - I'm trying to install the machine agent on linux, but it appears to look for the db-agent path. Am I missing something here?

#ansible-playbook -i hosts-linux machine.yaml

.
.
.

TASK [appdynamics.agents.logger : Copy the log4j file down to update it localy] *************************************************************************
fatal: [10.0.110.37]: FAILED! => {"changed": false, "msg": "file not found: /opt/appdynamics/db-agent/conf/logging/log4j.xml"}

[jpadmin]

You won't face that issue if you try to run the automation using latest version ansible

[iogbole]

FYI @v-zhuravlev

[v-zhuravlev]

hi @pk-z1 , thanks for reporting. It Would be great if you can provide more info in order to replicate this issue:
ansible version
appdynamics-ansible collection version
machine.yaml contents if it is custom playbook
any machine agent related variables you may set elsewhere( in inventory, vars file etc)

@jpadmin , do you mean ansible version or collection version?

[v-zhuravlev]

Can confirm this error for ansible 2.9, here is the new test for it
https://github.com/Appdynamics/appdynamics-ansible/runs/2679542023?check_suite_focus=true#step:7:738

[v-zhuravlev]

as a workaround, please upgrade to 2.10 + or remove agent_log_level: debug from vars or change to info

[pk-z1]

Thanks @v-zhuravlev - I also validated that agent_log_level: "info" works as well.

[jpadmin]

@v-zhuravlev , I can confirm that the automation works perfectly using latest ansible software with python3 as the interpreter

[v-zhuravlev]

Found what was the issue in 2.9. Fixed in #72 . Will be available in the next release.

[v-zhuravlev]

available in 21.6.0