To resolve this, you'll need to adjust the SELinux policies to allow the necessary access.

One way to do this is by creating a custom policy module that allows the access that Deploy Agent requires. You can generate a local policy module to allow this access with the following steps:

1. Check the SELinux audit log (`/var/log/audit/audit.log`) for denied entries related to your Deploy Agent.
2. Use the **audit2allow** utility to generate a custom policy module. You can do this by running `grep deploy /var/log/audit/audit.log | audit2allow -M myDeployAgent`.
3. Load the newly created policy module with `semodule -i myDeployAgent.pp`.