Skip to content

The installation of multiple hosts that are mixed Universal Forwarder and Full installation does not work and only full is performed. #176

@n0mer1

Description

@n0mer1

If I run a playbook with the install tasks on 3 instances where one is the Splunk server with the full installation and 2 of them are universal forwarders (uf), only the steps for full is performed when it comes to download and unarchive:

TASK [splunk.splunk : debug] ***************************************************
ok: [splunk] => {
    "msg": "The filename that will be downloaded is splunk-9.0.3-dd0128b1f8cd-Linux-x86_64.tgz"
}
ok: [test-host] => {
    "msg": "The filename that will be downloaded is splunkforwarder-9.0.3-dd0128b1f8cd-Linux-x86_64.tgz"
}
ok: [syslog-server] => {
    "msg": "The filename that will be downloaded is splunkforwarder-9.0.3-dd0128b1f8cd-Linux-x86_64.tgz"
}

TASK [splunk.splunk : debug] ***************************************************
ok: [splunk] => {
    "msg": "The upgrade file will be downloaded to /tmp/splunk-9.0.3-dd0128b1f8cd-Linux-x86_64.tgz"
}
ok: [test-host] => {
    "msg": "The upgrade file will be downloaded to /tmp/splunkforwarder-9.0.3-dd0128b1f8cd-Linux-x86_64.tgz"
}
ok: [syslog-server] => {
    "msg": "The upgrade file will be downloaded to /tmp/splunkforwarder-9.0.3-dd0128b1f8cd-Linux-x86_64.tgz"
}

TASK [splunk.splunk : Download Splunk full package] ****************************
ok: [splunk -> localhost]

TASK [splunk.splunk : Unarchive Splunk full package to /opt/splunk] ************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: If you are using a module and expect the file to exist on the remote, see the remote_src option
fatal: [syslog-server]: FAILED! => {"changed": false, "msg": "Could not find or access '/tmp/splunkforwarder-9.0.3-dd0128b1f8cd-Linux-x86_64.tgz' on the Ansible Controller.\nIf you are using a module and expect the file to exist on the remote, see the remote_src option"}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: If you are using a module and expect the file to exist on the remote, see the remote_src option
fatal: [test-host]: FAILED! => {"changed": false, "msg": "Could not find or access '/tmp/splunkforwarder-9.0.3-dd0128b1f8cd-Linux-x86_64.tgz' on the Ansible Controller.\nIf you are using a module and expect the file to exist on the remote, see the remote_src option"}
changed: [splunk]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions