-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seems like issue in set_config_stanza.yml #751
Comments
issue still in 9.1.1 |
thanks @yaroslav-nakonechnikov for raising the request and suggesting the fix. I am working with splunk-operator team to test the fix. |
I face the same issue. Thanks for working on it! |
this one looks like fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
while working with splunk-operator (splunk/splunk-operator#1212), looks like i found logical issue somehwere there:
https://github.com/splunk/splunk-ansible/blob/076537346517070a222e37bd2b3a87c528a14eb9/roles/splunk_common/tasks/set_config_stanza.yml#L20C1-L21C1
problem: when pod restars, value is empty, which creates broken config.
possible solution: check if key with value already exist.
The text was updated successfully, but these errors were encountered: