-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix listCapacity sort by usage #11316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.19 #11316 +/- ##
=========================================
Coverage 15.17% 15.17%
- Complexity 11362 11364 +2
=========================================
Files 5415 5415
Lines 476030 476043 +13
Branches 58115 58117 +2
=========================================
+ Hits 72246 72255 +9
- Misses 395701 395703 +2
- Partials 8083 8085 +2
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:
|
sureshanaparti
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clgtm
|
@blueorangutan package |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes a bug in the listCapacity API where the sort by usage parameter was not working correctly. The issue was that when sorting by usage, the comparator would fall back to sorting by capacity type even when a specific sort parameter was provided.
- Fixes comparator logic to respect the sortBy parameter when zones have the same name
- Prevents unintended fallback to capacity type sorting when sortBy is specified
api/src/main/java/org/apache/cloudstack/api/command/admin/resource/ListCapacityCmd.java
Outdated
Show resolved
Hide resolved
|
@blueorangutan package |
|
@borisstoyanov 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 ✔️ debian ✔️ suse15. SL-JID 14436 |
|
@blueorangutan test |
|
@borisstoyanov a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
@blueorangutan package |
|
@abh1sar 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. |
DaanHoogland
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clgtm
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 14439 |
|
[SF] Trillian test result (tid-13961)
|
borisstoyanov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, manually checked it
Description
This PR fixes listCapacity api's sort by usage parameter.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Before:
After:
How did you try to break this feature and the system with this change?