Deployment Client downloads configuration from local dir on DS to default dir on client.

[bmarona]

Hello All,

We are facing the problem with Deployment server and maybe one of you met with such DS behavior in past. 

All HF instances are with Splunk Enterprise 7.3.3 and they are connected with Deployment Server with the same Splunk version. We have apps with content created in local directory (totally custom apps and modified apps from Splunk Base as well) placed in deployment-apps directory. When we install the app on clients in server class then that app is downloaded by clients in correct way - content from default is placed in default directory, configuration from local is placed in local directory on client . The issue shows up when we modify those apps on DS and reload deploy-server. Then modified configuration from local dir is placed in default on clients. The problem is because old content is still in local on client and new configuration is ignored because local has higher priority.

I tried to search in splunkd.log on both - client and DS - but unfortunately there is nothing interesting related to DS.

Thanks,
Bart

[bmarona · Accepted solution]

Hi,

I know what was the issue. I found in one app a serverclass.conf file with stanza:
[global]
excludeFromUpdate = $app_root$/local
The setting was no longer needed so i have disabled it and DS deploys configuration to Splunk local dir.

[bmarona]

Thanks for advise but the behavior is the same even when i have fully custom app (only local dir in it). First installation is ok, everything is located in local on client (like on DS), after any modification on DS side and splunk reload deploy-server configuration is downloaded to to default.

[thambisetty]

this sounds interesting, I have never come across this type of problem with DS. I would recommend you to have only local, remove default if possible.