Splunk Indexer Clustering Issues- How to resolve error [00000100]?

[govindashwin8]

I am trying to set up an indexer cluster with one master, 2 indexers and a search head, using splunk enterprise version 7.2.3.
After configuring the master and the indexers I see the indexers as sick 

Error [00000100] Instance name "xxxxx-1001264746-1-1088387397" REST interface to peer is not responding. Check var/log/splunk/splunkd_access.log on the peer. 

On the access logs :-

10.236.9.173 - splunk-system-user [25/Dec/2020:00:46:54.047 +0000] "GET /services/admin/bundles/xxxxx-1001264746-3-1088390176?count=-1 HTTP/1.1" 404 174 - - - 0ms

I see the following messages on the splunkd log in the master. 

12-25-2020 00:37:54.055 +0000 WARN GetBundleListTransaction - Server xxxxx-1001264746-1-1088387397[https://10.236.9.46:8089/services/admin/bundles/xxxxx-1001264746-3-1088390176] does not support bundle version listing. Probably an older version. Giving up due to error code 404.
12-25-2020 00:37:54.055 +0000 WARN DistributedPeer - Peer:https://10.236.9.46:8089 Unable to get bundle list
12-25-2020 00:37:54.056 +0000 WARN DistributedPeerManager - Cannot determine a latest common bundle, search may be blocked
12-25-2020 00:37:54.056 +0000 WARN GetBundleListTransaction - Server xxxxx-1001264746-2-1088388970[https://10.236.9.48:8089/services/admin/bundles/xxxxx-1001264746-3-1088390176] does not support bundle version listing. Probably an older version. Giving up due to error code 404.
12-25-2020 00:37:54.056 +0000 WARN DistributedPeer - Peer:https://10.236.9.48:8089 Unable to get bundle list
12-25-2020 00:37:54.057 +0000 WARN DistributedPeerManager - Cannot determine a latest common bundle, search may be blocked

Has someone seen or faced this issue before. Any help is much appreciated.

Thanks.

[venugoski]

Hi @govindashwin8  did you find resolution for the issue?