Sergey Nuyanzin created FLINK-39002:
---------------------------------------
Summary: Could not resolve ResourceManager because of NPE
Key: FLINK-39002
URL: https://issues.apache.org/jira/browse/FLINK-39002
Project: Flink
Issue Type: Bug
Components: Deployment / Kubernetes, Tests
Reporter: Sergey Nuyanzin
e2e tests 2 are failing with
{noformat}
[pekko.ssl.tcp://flink@localhost:6123]] Caused by:
[javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is
disabled or cipher suites are inappropriate)]
2026-01-30 00:57:11,259 INFO
org.apache.flink.runtime.taskexecutor.TaskExecutor [] - Could not
resolve ResourceManager address
pekko.ssl.tcp://flink@localhost:6123/user/rpc/resourcemanager_*, retrying in
10000 ms: Could not connect to rpc endpoint under address
pekko.ssl.tcp://flink@localhost:6123/user/rpc/resourcemanager_*.
{noformat}
including master
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=71966&view=logs&j=ef799394-2d67-5ff4-b2e5-410b80c9c0af&t=9e5768bc-daae-5f5f-1861-e58617922c7a&s=ab6e269b-88b2-5ded-2544-4aa5b1124530
I noticed there were similar issues in past, however none of them failed with
NPE so far.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
