The GitHub Actions job "Flink Kubernetes Operator CI" on 
flink-kubernetes-operator.git/FLINK-40246-logback-slf4j2 has failed.
Run started by GitHub user spuru9 (triggered by spuru9).

Head commit for run:
0873a9da69803353ee26839bd02394252eb00ff2 / Purushottam Sinha 
<[email protected]>
[FLINK-40246] Migrate logging stack to SLF4J 2.x and bump Logback to 1.5.34

Logback 1.2.13 is the terminal release of an EOL line, so the CVEs filed
against it (CVE-2024-12798, CVE-2024-12801, CVE-2025-11226, CVE-2026-1225,
CVE-2026-9828, CVE-2026-10532) have no fix on that branch. Every patched
Logback release targets SLF4J 2.x, so clearing them requires moving the
whole logging stack off slf4j-api 1.7.36.

The 1.7.36 pin is independently incorrect. JOSDK 5.5.0 and fabric8 7.8.0
both declare slf4j-api 2.0.18, and JOSDK's
ReconciliationDispatcher.handleErrorStatusHandler calls
Logger.atLevel(Level), which does not exist in 1.7.36. A FlinkStateSnapshot
whose reconcile fails and whose error-status patch then also fails throws
NoSuchMethodError from inside the error handler, masking the original
failure.

- slf4j-api 1.7.36 -> 2.0.18, logback 1.2.13 -> 1.5.34
- log4j-slf4j-impl -> log4j-slf4j2-impl across all modules, including the
  dependency-plugin item that stages the binding into the image
- declare logback-core as a provided dependency rather than only as a
  dependency-plugin artifact item
- drop log4j-slf4j-impl from the operator NOTICE (provided since
  FLINK-39501, so never bundled) and refresh the slf4j-api versions
- rewrite the logging docs hint: it described the old constraint with the
  wrong failure mode, since SLF4J falls back to a NOP logger rather than
  throwing ClassNotFoundException

Report URL: 
https://github.com/apache/flink-kubernetes-operator/actions/runs/31013933521

With regards,
GitHub Actions via GitBox

Reply via email to