-
Notifications
You must be signed in to change notification settings - Fork 1.2k
linstor: fix getVolumeStats if multiple Linstor primary storages are used #11397
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
linstor: fix getVolumeStats if multiple Linstor primary storages are used #11397
Conversation
…used We didn't account for caching the volume stats for each used Linstor cluster, so the first asked Linstor cluster would prevent caching for all the others and so null was returned. Now we have invalidate counters for each Linstor cluster and also store the cache result with the Linstor cluster address prefixed.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.19 #11397 +/- ##
=========================================
Coverage 15.18% 15.18%
- Complexity 11363 11369 +6
=========================================
Files 5415 5415
Lines 476061 476066 +5
Branches 58122 58123 +1
=========================================
+ Hits 72269 72276 +7
+ Misses 395702 395701 -1
+ Partials 8090 8089 -1
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:
|
|
@blueorangutan package |
|
@sureshanaparti 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 14636 |
|
linsor plugin changes only, @rp- confirmed tests with linsor. |
…used (apache#11397) We didn't account for caching the volume stats for each used Linstor cluster, so the first asked Linstor cluster would prevent caching for all the others and so null was returned. Now we have invalidate counters for each Linstor cluster and also store the cache result with the Linstor cluster address prefixed.
|
@weizhouapache I just noticed that this commit seems to be missing on the |
|
@rp- |
Ah ok, sorry, I was looking for the commit message...., but it was hidden behind the "Merge ...." message |
Description
We didn't account for caching the volume stats for each used Linstor cluster, so the first asked Linstor cluster would prevent caching for all the others and so null was returned.
Now we have invalidate counters for each Linstor cluster and also store the cache result with the Linstor cluster address prefixed.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
ACS cluster with 2 different Linstor clusters
How did you try to break this feature and the system with this change?