DRILL-8550: Fix Flaky Splunk Tests#3060
Merged
Merged
Conversation
The splunk/splunk:9.3 tag was republished on 2026-07-01 to point at 9.3.14, turning CI red on every branch. Identical test code passed on 2026-06-26 against 9.3.13 and fails on 9.3.14, so the image is the only variable. 9.3.14 serves HTTPS on the management port despite SPLUNKD_SSL_ENABLE=false, so the plaintext client failed every connection with "Unexpected end of file from server". Disabling splunkd SSL is a path Splunk has regressed repeatedly (splunk/docker-splunk#639, still open), so talk to the default HTTPS listener instead and turn off certificate and hostname validation for the self-signed container cert. Pin the patch version so an upstream push cannot break the build on its own. Also correct the constructor argument comment, which listed five names for six values and hid validateHostname=true on the shared-user config.
cgivre
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
The Splunk unit tests have been failing consistently on CI. The
splunk/splunk:9.3tag was republished on 2026-07-01 to point at 9.3.14. Identical test code passed on 2026-06-26 against 9.3.13 and fails on 9.3.14, so the image is the only variable.9.3.14 serves HTTPS on the management port despite
SPLUNKD_SSL_ENABLE=false, so the plaintext client failed every connection withUnexpected end of file from server. Shockingly, despite Splunk's incredible commitments to code and design quality, disabling splunkd SSL is a path Splunk has regressed repeatedly, so this talks to the default HTTPS listener instead and turns off certificate and hostname validation for the self-signed container cert.The patch version is now pinned so an upstream push cannot break the build on its own.
Also corrects the constructor argument comment, which listed five names for six values and hid
validateHostname=trueon the shared-user config.Changes
SplunkTestSuite: pin image tosplunk/splunk:9.3.14, dropSPLUNKD_SSL_ENABLE=false, connect overhttps, and setvalidateCertificates=false/validateHostname=falseon both plugin configs.Documentation
No user-facing changes; test-only.
Testing
contrib/storage-splunktest sources compile. The suite requires Docker to run the Splunk container.Cherry-picked from #3037 (commit 24cbbdf).