Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Splunk Operator: Could not get the Cluster Manager Image. #1348

Closed
TheFausap opened this issue Jul 10, 2024 · 5 comments
Closed

Splunk Operator: Could not get the Cluster Manager Image. #1348

TheFausap opened this issue Jul 10, 2024 · 5 comments
Assignees
Labels

Comments

@TheFausap
Copy link

Please select the type of request

Bug

Tell us more

Describe the request
After an update to a cluster bundle the repo, adding some remote volumes, the cluster manager started a rolling restart as expected, but all the indexers are now down. In the events of the indexer CSV I found this error

Could not get the Cluster Manager Image. Stateful set spl-cm-cluster-manager not found.

Of course, the stateful set is there up and running, and my cluster manager is up and running.

Expected behavior

  • After the rolling restart the cluster should be up with all the peers.

Splunk setup on K8S

  • Splunk is using the operation version 2.5.1 under RedHat Openshift 4.14.29
@michal-tatusko-splunk
Copy link
Collaborator

Thank you for raising this bug. We will look into that shortly.

@vivekr-splunk vivekr-splunk assigned akondur and unassigned jryb Oct 22, 2024
@akondur akondur removed the Q3 2024 label Oct 22, 2024
@vivekr-splunk
Copy link
Collaborator

@TheFausap can you provide us more details with regard to this issue. please share the indexer log files. and Custom resource

@akondur
Copy link
Collaborator

akondur commented Dec 10, 2024

Hi @TheFausap , could you please provide us with more details?

@TheFausap
Copy link
Author

Hi @akondur I cannot give you too much information right now, because we uninstalled the operator and after the re-installation, everything was back to normal. At the moment this error is not happening anymore. I don't know if you want to keep this issue open, or we could close it and I will reopen a new one if this error pops up again.

@michal-tatusko-splunk
Copy link
Collaborator

Hello @TheFausap,
I am glad to hear you are no longer experiencing the issues. I will close it, as there's no way to reproduce this bug. Please feel free to reopen the issue if the behavior occurs again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants