CSPL-4281 Add fallback error handling for cluster manager multisite configuration #1629
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes cluster manager reconciliation failures when multisite detection fails during initial deployment. Previously, the cluster manager would get stuck in Error phase because it tried to query its own pod before it was ready.
Key Changes
pkg/splunk/enterprise/clustermanager.goVerifyCMisMultisiteCall→GetCMMultisiteEnvVarsCallGetClusterInfo()failsTest Files
clustermanager_test.goandupgrade_test.goTesting and Verification
Issue: Test timeouts with cluster manager stuck in Error phase for 4+ hours
Fix: Returns fallback env vars so reconciliation continues even when CM pod not ready
Expected: MC ConfigMap always receives cluster manager URL; multisite info added when pod becomes ready
Related Issues
CSPL-4281: Fix stale peer CM config issue
PR Checklist