Fixes issues with configure_dmc.yml #205
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes an issue where the DMC is not automatically configured in Distributed mode because of the lack of the
local
directory referenced for the file{{ splunk_home }}/etc/apps/splunk_monitoring_console/local/splunk_monitoring_console_assets.conf
inconfigure_dmc.yml
. This fix makes sure the directory exists before creating the file, ensuring that the subsequent task doesn't fail.Also fixes an issue where Splunk returns a non-zero exit code when you add a peer to the DMC as a search peer which is already there (rc 24), and logs as such. This no longer fails the task, and instead just doesn't log a change to the ansible worker.
Also fixes issue #197
Changed
roles/splunk/tasks/configure_dmc.yml