Open nhinds opened 4 days ago
@nhinds thanks for opening up this issue! You are absolutely correct and that was an oversight on our part.
Glad you found a workaround, you could also set falcon_api_sensor_download_cleanup: false
as well to prevent the deletion.
I think we need to consider moving the deletion operation towards the end of the role after the sensor actually get's installed, whether remote or locally to prevent this situation. Will look into a PR next week.
When running version 4.7.1 of the
crowdstrike.falcon.falcon_install
role against alocalhost
inventory, the RPM gets deleted before it is installed.It seems like #569 changed the defaults so that location the RPM is downloaded to on the controller (
falcon_api_sensor_download_path
) and the location the RPM is copied to on the Linux target machine (falcon_install_tmp_dir
) are both/tmp/falcon-sensor
. When run against an inventory oflocalhost
(i.e. when using Ansible to install Falcon on the current machine), this results in:/tmp/falcon-sensor/falcon-sensor-*.rpm
/tmp/falcon-sensor/falcon-sensor-*.rpm
is copied to itself/tmp/falcon-sensor/falcon-sensor-*.rpm
Overriding
falcon_api_sensor_download_path
so it is different thanfalcon_install_tmp_dir
(e.g.falcon_api_sensor_download_path: "/tmp/falcon-sensor-download"
) allows the installation to succeed.