Fix filter and pagination on API findStoragePoolsForMigration - #8306
DaanHoogland merged 1 commit into
Conversation
|
@GaOrtiga should there be some UI change for this as well? |
@DaanHoogland It will not be necessary; the UI issues were a result of pagination problems within the API, which have now been resolved. Therefore, addressing the API issues fixed the problems encountered in the UI aswell. I will edit the description of the PR to include screenshots of the before and after. |
de702eb to
abbb904
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #8306 +/- ##
============================================
+ Coverage 22.25% 23.14% +0.89%
- Complexity 22439 23485 +1046
============================================
Files 5117 5117
Lines 346819 346830 +11
Branches 49790 49793 +3
============================================
+ Hits 77190 80283 +3093
+ Misses 258466 255009 -3457
- Partials 11163 11538 +375
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
JoaoJandre
left a comment
There was a problem hiding this comment.
LGTM, tested the pagination on the UI and it works as expected now.
|
@blueorangutan package |
|
@rohityadavcloud 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. |
|
@blueorangutan test keepEnv |
|
@DaanHoogland a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
the usual suspects in the smoke test results:
tested only with keyword search, but lgtm |
GutoVeronezi
left a comment
There was a problem hiding this comment.
CLGTM
I just pointed out an optional small improvement.
Co-authored-by: Gabriel <gabriel.fernandes@scclouds.com.br>
Description
When utilizing the
findStoragePoolsForMigrationAPI, ACS disregards the specified parameterskeyword,page, andpagesize, returning all compatible storages for the volume. This issue also affected the UI, causing every available result to be shown during a migration, regardless of the filters or pagination applied.To address this, modifications were implemented in the API to ensure the provided parameters are respected, guaranteeing that only the appropriate results are exhibited.
UI before
UI after
Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
I tried migrating volumes both through the API and the UI and both worked accordingly.