You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
listBackupOfferings API: keyword parameter does not filter results #12466
The keyword parameter in the listBackupOfferings API is accepted but does not filter results. Regardless of the search term provided, the API returns an empty result set.
Interesting catch on this filtering bug. Looking at the issue, it seems the keyword parameter is accepted by the API but not actually used in the search criteria implementation.
A few thoughts for investigation:
The problem is likely in BackupManagerImpl.java where the search logic needs to check if keyword is provided and apply it to the name/description filtering
Similar list APIs in CloudStack probably handle this correctly - might be worth checking how listServiceOfferings or listComputeOfferings implement their keyword filtering for reference
The reproduction steps are clear - creating a test case with 3 offerings and verifying each keyword returns empty vs the expected filtered result would validate the fix
Worth checking if this is just a missing null/empty check on the keyword parameter or if the filtering logic itself wasn't connected. The fact that other parameters work correctly suggests it's isolated to the keyword implementation.
Activity
saturn-amarbat commentedon Jan 22, 2026
Interesting catch on this filtering bug. Looking at the issue, it seems the keyword parameter is accepted by the API but not actually used in the search criteria implementation.
A few thoughts for investigation:
keywordis provided and apply it to the name/description filteringlistServiceOfferingsorlistComputeOfferingsimplement their keyword filtering for referenceWorth checking if this is just a missing null/empty check on the keyword parameter or if the filtering logic itself wasn't connected. The fact that other parameters work correctly suggests it's isolated to the keyword implementation.
adithyanms-debug commentedon Jan 26, 2026
Hi there, I am new to open source contribution is it a good issue to start working
DaanHoogland commentedon Jan 26, 2026
it would have been for sure @adithyanms-debug , but please see #12480 , it seems to have already been implemented.
adithyanms-debug commentedon Jan 26, 2026
@DaanHoogland thanks for letting me know
chezsan770 commentedon Jan 26, 2026
Hi, I’d like to work on this issue if it’s still open.
Please let me know if I can proceed.
DaanHoogland commentedon Jan 27, 2026
@chezsan770 there is a PR ready for this, it just needs backpporting to the 4.20 branch (if the author, @JeevanYewale is willing)
DaanHoogland commentedon Jan 28, 2026
fixed in #12540