server: fix vm_stats records are not removed if batchsize is 0#9818
server: fix vm_stats records are not removed if batchsize is 0#9818yadvr merged 1 commit intoapache:mainapache/cloudstack:mainfrom weizhouapache:4.20-fix-vm_stats-cleanupweizhouapache/cloudstack:4.20-fix-vm_stats-cleanupCopy head branch name to clipboard
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9818 +/- ##
=========================================
Coverage 15.78% 15.78%
- Complexity 12564 12565 +1
=========================================
Files 5627 5627
Lines 492266 492250 -16
Branches 63860 63795 -65
=========================================
+ Hits 77707 77710 +3
+ Misses 406084 406066 -18
+ Partials 8475 8474 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
@blueorangutan package |
|
@weizhouapache 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. |
|
related to |
|
@weizhouapache We need this change in 4.19 since the PRs you mentioned are part of 4.19 branch. |
4.19 has similar change introduced in #8740 , it works |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 11379 |
|
@blueorangutan test |
|
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-11682)
|
|
@blueorangutan test |
|
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
host_ha test failures are intermittent in nature. Let's merge this for sake of time & kick test matrix on the health check PR cc @JoaoJandre |
|
[SF] Trillian test result (tid-11686)
|
Description
Prior to this change
With this change
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?