Improve the debug logs for insufficient IOPS on storage allocation#13579
Improve the debug logs for insufficient IOPS on storage allocation#13579nvazquez wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 4.22 #13579 +/- ##
=========================================
Coverage 17.67% 17.67%
- Complexity 15797 15798 +1
=========================================
Files 5923 5923
Lines 533349 533354 +5
Branches 65248 65249 +1
=========================================
+ Hits 94253 94259 +6
+ Misses 428437 428436 -1
Partials 10659 10659
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:
|
|
@blueorangutan package |
|
@nvazquez a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 18522 |
|
@blueorangutan test |
|
@nvazquez a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-16519)
|
Description
This PR improves the logging messages on storage pool allocation for insufficient IOPS.
Add a debug log at the point of failure with
capacityIops,usedIopsandrequestedIops.The message follows the same style as the existing "Insufficient un-allocated capacity on: X for storage allocation, ..." logs in
checkPoolforSpace, so both read the same way when grepping allocation traces.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?