semlanghi opened a new issue, #1336:
URL: https://github.com/apache/flink-agents/issues/1336

   ### Search before asking
   
   - [x] I searched in the 
[issues](https://github.com/apache/flink-agents/issues) and found nothing 
similar.
   
   ### Description
   
   #296 / #298 taught the **Python** runtime to load the legacy Flink config 
file `flink-conf.yaml`
   (`python/flink_agents/runtime/remote_execution_environment.py`). The 
**Java** runtime never got the
   same fallback: `RemoteExecutionEnvironment.loadAgentConfiguration` reads only
   `$FLINK_CONF_DIR/config.yaml` and throws if it is missing.
   
   Flink 1.20 distributions and deployments that still ship the legacy 
`flink-conf.yaml` (and no
   `config.yaml`) therefore cannot run any Java Flink Agents job. It fails 
while the job graph is being
   built:
   
   ```
   java.lang.RuntimeException: Failed to load Flink Agents configuration from 
/opt/flink/conf
       at 
org.apache.flink.agents.runtime.env.RemoteExecutionEnvironment.loadAgentConfiguration
       at org.apache.flink.agents.runtime.env.RemoteExecutionEnvironment.<init>
   Caused by: java.io.FileNotFoundException: /opt/flink/conf/config.yaml (No 
such file or directory)
   ```
   
   ### How to reproduce
   
   1. Use a Flink 1.20.3 standalone cluster whose `conf/` directory contains 
`flink-conf.yaml` but no
      `config.yaml`.
   2. Submit any Java job that builds an agent through
      `AgentsExecutionEnvironment.getExecutionEnvironment(env)`.
   3. Job submission fails with the exception above.
   
   ### Version and environment
   
   - Flink 1.20.3, JDK 17
   - Flink Agents 0.2.1, 0.3.x, and `main` / `release-0.4.0-rc1` (as of 
2026-10-28)
   
   ### Are you willing to submit a PR?
   
   - [x] I'm willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to