splunk / splunk/splunk-ansible
Master node container playbook fails "Rolling restart of the peers is in progress"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 402
- Forks
- 205
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 6
Description
While performing a docker run of the master node container on an already established cluster (re-deployment), the playbook running inside the container fails to complete with the error "Rolling restart of the peers is in progress" and restarts the container. This becomes a loop and only breaks when all indexers in the cluster undergo a Splunk service restart. This behaviour is noted on container versions 7.3.3-redhat, 7.3.6-redhat and 8.1.3.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing a docker run redeployment of the master node container on an established cluster using one of the listed Splunk container versions. Trace the playbook step that reports "Rolling restart of the peers is in progress" and compare its behavior with the indexers' Splunk service state. Done means the playbook completes without repeatedly restarting the container, without requiring manual restarts of all indexers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, docker, python
- Domain
- devops, distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100