-
Notifications
You must be signed in to change notification settings - Fork 567
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.
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
fix: advertised address should fall back to configured address #9669
Conversation
If no advertised host and port are configured, we need to fall back to the configured host and port and not to the default host and port.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Ole 👍
I would like to have an integration test which fails without the fix actually, and/or that we use the StandaloneVateway setup code in our QA IT ClusterRule. Not sure whether we want to do that as follow up but it would be good to have it.
|
||
// then | ||
assertThat(actual.getCluster().getAdvertisedHost()).isEqualTo(expectedHost); | ||
assertThat(actual.getCluster().getAdvertisedPort()).isEqualTo(Integer.parseInt(expectedPort)); |
Check notice
Code scanning / CodeQL
Missing catch of NumberFormatException
I agree, but I'd like to do this as a follow up since I'd like to include this fix in the next alpha release. See #9670 |
Add regression test which fails on SNAPSHOT, the job notification is missed in that case. With the fix the test is green.
I created an integration test (regression test), which fails with SNAPSHOT and is green with |
qa/integration-tests/src/test/java/io/camunda/zeebe/it/clustering/LongPollingIT.java
Outdated
Show resolved
Hide resolved
Co-authored-by: Nicolas Pepin-Perreault <43373+npepinpe@users.noreply.github.com>
bors r+ |
Build succeeded: |
Description
Since we introduced support for advertised addresses in the gateway in #9572, the atomix communication services were bound to the default host and port (0.0.0.0:26502) if no advertised address was configured instead of falling back to the configured host and port first.
Related issues
closes #9658 because job available notifications were not received which caused the delay in job activation.