Skip to content

CSPL-4715: fix empty pod name in ClusterManager bundle push#1849

Merged
kubabuczak merged 1 commit intodevelopfrom
CSPL-4715-fix-empty-pod-name-bundle-push
Apr 16, 2026
Merged

CSPL-4715: fix empty pod name in ClusterManager bundle push#1849
kubabuczak merged 1 commit intodevelopfrom
CSPL-4715-fix-empty-pod-name-bundle-push

Conversation

@kubabuczak
Copy link
Copy Markdown
Collaborator

Description

Fixes a 3.1.0 regression where PerformCmBundlePush receives a podExecClient with an empty targetPodName, causing Pod "" not found errors that block bundle push, app framework, and SmartStore config checks.

Key Changes

  • pkg/splunk/enterprise/clustermanager.go — set correct CM pod name on podExecClient at creation
  • pkg/splunk/enterprise/names.go — trailing whitespace cleanup

Testing and Verification

  • Existing unit tests pass

Related Issues

PR Checklist

  • Code changes adhere to the project's coding standards
  • Relevant unit and integration tests are included
  • Documentation has been updated accordingly
  • If test framework files were changed, docs/IntegrationTesting.md has been updated
  • All tests pass locally
  • The PR description follows the project's guidelines

Set targetPodName when creating podExecClient in ApplyClusterManager
so PerformCmBundlePush resolves the correct pod even when addTelApp
is skipped (telAppInstalled == true).
@kubabuczak kubabuczak merged commit d0c6386 into develop Apr 16, 2026
51 checks passed
@kubabuczak kubabuczak deleted the CSPL-4715-fix-empty-pod-name-bundle-push branch April 16, 2026 18:30
@github-actions github-actions bot locked and limited conversation to collaborators Apr 16, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants