You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running a distributed splunk set up utilizing pod man and splunk docker containers 9.3.2 everything is working up and index or cluster index manager search head cluster are all up and connected. My index manager is also the license server and deployer the only issue I'm having is with my index manager like I said it is all up and up, but when I stop my index manager container and then remove it, I then re-deploy the container from the same Yamo file with persistent storage, so nothing is changing the container wants to error out in the pre flight ansible check and splunk is recognizing it as an upgrade and is trying to upgrade to the version that it's on 9.3.2
The text was updated successfully, but these errors were encountered:
I can log in via the container, restart splunk from inside and go through migration questions. It then comes up fine and everything connects. Trying to figure out why the indexer manager thinks it's migrating to new version everyone I start a new container
I am running a distributed splunk set up utilizing pod man and splunk docker containers 9.3.2 everything is working up and index or cluster index manager search head cluster are all up and connected. My index manager is also the license server and deployer the only issue I'm having is with my index manager like I said it is all up and up, but when I stop my index manager container and then remove it, I then re-deploy the container from the same Yamo file with persistent storage, so nothing is changing the container wants to error out in the pre flight ansible check and splunk is recognizing it as an upgrade and is trying to upgrade to the version that it's on 9.3.2
The text was updated successfully, but these errors were encountered: