Skip to content

Persist SPLUNK_INDEXER_URL in MC ConfigMap #1815

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.

Sign up for GitHub

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

Open
Igor-splunk wants to merge 1 commit into
base: develop
Choose a base branch
from

persist SPLUNK_INDEXER_URL in MC ConfigMap

f2122f0
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Open

Persist SPLUNK_INDEXER_URL in MC ConfigMap #1815

persist SPLUNK_INDEXER_URL in MC ConfigMap
f2122f0
Select commit
Loading
Failed to load commit list.
GitHub Actions / Smoke Test Results - managersecret failed Apr 3, 2026 in 0s

314 tests run, 3 passed, 310 skipped, 1 failed.

Annotations

Check failure on line 1 in Running secret-jjz

See this annotation in the file changed.

@github-actions github-actions / Smoke Test Results - managersecret

Running secret-jjz.[It] Secret Test for SVA C3 Clustered deployment (C3 - clustered indexer, search head cluster) managersecret, smoke, c3: secret update on indexers and search head cluster 

A suite timeout occurred
Raw output 
[TIMEDOUT] A suite timeout occurred
In [It] at: /home/runner/work/splunk-operator/splunk-operator/test/secret/manager_secret_c3_test.go:58 @ 04/03/26 16:42:00.962

This is the Progress Report generated when the suite timeout occurred:
  Secret Test for SVA C3 Clustered deployment (C3 - clustered indexer, search head cluster) managersecret, smoke, c3: secret update on indexers and search head cluster (Spec Runtime: 3h32m1.022s)
    /home/runner/work/splunk-operator/splunk-operator/test/secret/manager_secret_c3_test.go:58
    In [It] (Node Runtime: 3h32m0.876s)
      /home/runner/work/splunk-operator/splunk-operator/test/secret/manager_secret_c3_test.go:58

    Spec Goroutine
    goroutine 1109 [select]
      github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0002688c0, {0x2a719f0, 0xc00027ed30}, 0x1, {0x0, 0x0, 0x0})
        /home/runner/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558
      github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0002688c0, {0x2a719f0, 0xc00027ed30}, {0x0, 0x0, 0x0})
        /home/runner/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145
      github.com/splunk/splunk-operator/test/testenv.VerifyMonitoringConsoleReady({0x2a82ab8, 0x3eabea0}, 0xc000396bc0, {0xc00099d020, 0x12}, 0xc000e0a008, 0xc0006d2140)
        /home/runner/work/splunk-operator/splunk-operator/test/testenv/verificationutils.go:86
    > github.com/splunk/splunk-operator/test/secret.init.func1.3.1()
        /home/runner/work/splunk-operator/splunk-operator/test/secret/manager_secret_c3_test.go:153
          | 
          | // Verify Monitoring Console is Ready and stays in ready state
          > testenv.VerifyMonitoringConsoleReady(ctx, deployment, deployment.GetName(), mc, testcaseEnvInst)
          | 
          | // Verify RF SF is met
      github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0xc0009ac7e0?, 0xc000a6aed0?})
        /home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.1/internal/node.go:585
      github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()
        /home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.1/internal/suite.go:946
      github.com/onsi/ginkgo/v2/internal.(*Suite).runNode in goroutine 63
        /home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.1/internal/suite.go:911

There were additional failures detected after the initial failure. These are visible in the timeline
View more details on GitHub Actions