[8.19] (backport #8215) fix(diagnostics): handle log rotation races #8228
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Handle a race condition that can occur in Agent diagnostics if log rotation happens while logs are being zipped. There is a time window between when
filepath.WalkDir
reads the directory contents and when log files are opened for reading. During this time window, log rotation can happen, resulting in files that no longer exist and cannot be added to the diagnostic archive.To handle this,
fs.ErrNotExist
errors are ignored when attempting to add log files.Why is it important?
This race can happen at any time, so any user could be affected. The problem is worse if debug logging is enabled and logs are being rotated quickly.
Checklist
./changelog/fragments
using the changelog toolScreenshots
This is the user reported error:
via OCR, it says:
Disruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself
This is an automatic backport of pull request #8215 done by [Mergify](https://mergify.com).