Fix S3 carve cleanup never running and panic on empty carves (#43045)#46462
Fix S3 carve cleanup never running and panic on empty carves (#43045)#46462juan-fdz-hawa wants to merge 1 commit into
Conversation
Fixed a bug where the carve cleanup cron job called the MySQL implementation instead of the S3-aware implementation on S3-configured deployments, meaning expired carves were never marked as expired in S3. Also fixed a panic in S3 carve cleanup that occurred when there were no non-expired carves.
CI Feedback 🧐A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #46462 +/- ##
==========================================
+ Coverage 66.78% 66.81% +0.02%
==========================================
Files 2803 2803
Lines 223565 223569 +4
Branches 11345 11345
==========================================
+ Hits 149309 149377 +68
+ Misses 60694 60616 -78
- Partials 13562 13576 +14
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Related issue: Resolves #43045
Fixed a bug where the carve cleanup cron job called the MySQL implementation instead of the S3-aware implementation on S3-configured deployments, meaning expired carves were never marked as expired in S3. Also fixed a panic in S3 carve cleanup that occurred when there were no non-expired carves.
Checklist for submitter
If some of the following don't apply, delete the relevant line.
changes/,orbit/changes/oree/fleetd-chrome/changes.See Changes files for more information.
Testing