quota: skip usage records registering the period a volume has been attached - #13936
Conversation
|
@blueorangutan package |
|
@winterhazel a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #13936 +/- ##
============================================
- Coverage 19.65% 19.65% -0.01%
+ Complexity 19803 19801 -2
============================================
Files 6368 6368
Lines 574935 574939 +4
Branches 70358 70359 +1
============================================
- Hits 113026 113012 -14
- Misses 449632 449652 +20
+ Partials 12277 12275 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 18930 |
|
I don't think the smoke tests are going to have much value here. This change is isolated to the Quota plugin, and no Marvin test covers the Quota processing. |
ok. cc @bernardodemarco could you please verify it ? |
Sure, I'll try to test it today |
bernardodemarco
left a comment
There was a problem hiding this comment.
lgtm, reproduced the tests described in the PR's description, all good
Description
This is a follow-up of #11531 and #13909.
With #11531, the Usage server can now create up to 2 usage records for a single volume for the same period; one registers the time the volume remained allocated, while the other the time it remained attached to an instance. This results in a duplicate Quota value calculation for the volume.
For now, skip the Quota calculation for the volume usage records associating it to an instance.
Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?