MartijnVisser opened a new pull request, #29324:
URL: https://github.com/apache/flink/pull/29324
## What is the purpose of the change
`YARNSessionFIFOSecuredITCase` fails when a container log is rolled on
startup, because the keytab login then sits in `jobmanager.log.1` or
`taskmanager.log.1` and the test only reads the live file. The rollover itself
is a product bug, FLINK-40833, with its own red test.
## Brief change log
- `verifyStringsInNamedLogFiles` also reads rolled files (`<file>.<n>`)
- `verifyResultContainsKerberosKeytab` checks once instead of polling for
60s; the poll never found the line later, all six master failures since
2026-09-14 ran it to the timeout
## Verifying this change
This change is already covered by existing tests, such as
`YARNSessionFIFOSecuredITCase`.
I forced the startup rollover locally by pre-creating each container's log
file before its JVM starts. That fails on 710bb463094 with the CI error, passes
with this change, and fails again when the old file name check is put back.
Unforced, in a Linux container: 3 of 10 runs failed on 710bb463094, each on a
split log; 0 of 10 failed with this change, with 12 split logs.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
- If yes, how is the feature documented? not applicable
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (please specify the tool below)
Generated-by: Claude Code (Claude Opus 5.5)
--
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]
