fix(ci): fix Pulsar TLS integration tests with latest image#25099
Merged
thomasqueirozb merged 7 commits intomasterfrom Apr 2, 2026
Merged
fix(ci): fix Pulsar TLS integration tests with latest image#25099thomasqueirozb merged 7 commits intomasterfrom
thomasqueirozb merged 7 commits intomasterfrom
Conversation
The `apachepulsar/pulsar:latest` image moved to a version that breaks TLS connectivity, causing `pulsar_happy_tls` and `consumes_event_with_tls` to fail consistently in CI. Pin to 4.1.3 to unblock the merge queue. Re-enabling `latest` is tracked in #25096. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
thomasqueirozb
added
the
no-changelog
thomasqueirozb
changed the base branch from
pront-disable-pulsar-integration-tests
to
master
pront
approved these changes
Apr 2, 2026
thomasqueirozb
commented
Apr 2, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Since apache/pulsar#25238, Pulsar standalone mode advertises the container's FQDN (the container ID) instead of
localhost. The Pulsar client reconnects to the advertised address during service discovery, causing TLS hostname verification to fail against the certificate'sDNS:pulsarSAN.Setting
advertisedAddress=pulsarexplicitly fixes the mismatch and allows reverting the image pin back tolatest.Vector configuration
NA
How did you test this PR?
Ran
./scripts/run-integration-test.sh -r 0 int pulsarlocally -- all 7 tests pass (including the two TLS tests that were failing).Change Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References