Hey again @banderson7,
Thanks for the additional details.
I just took a look at the 1.1.0 build on my dev server and am seeing these in $AppHome/metadata/local.meta versus $AppHome/metadata/default.meta . As a quick test, see if you can grep out the HEAD and = ====== from local.meta on your deployment server. If these tags are there, you can move local.meta from the deployment server into a temporary directory (e.g., /tmp/ ) then reload the Deployment Server ( $SPLUNK_HOME/bin/splunk reload deploy-server ) to push the update.
Off the top of my head, I'm not entirely sure why local.meta on the Deployment Server would end up in default.meta on the Search Heads in your Search Head Cluster (SHC), but "local" has file precedence over "default," so that's likely in the mix here...
As a last step/test after redeploying from the Deployment Server, try to grep out the tags from $AppHome/metadata/default.meta on a SH in your SHC to confirm that they were successfully replaced with the correct $AppHome/metadata/default.meta from the Deployment Server. Alternatively, check splunkd.log for evidence of the tags *after issuing the $SPLUNK_HOME/bin/splunk reload deploy-server
Looking forward to hearing your results,
AP
... View more