-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Linstor fix host picking #12047
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
base: 4.20
Are you sure you want to change the base?
Linstor fix host picking #12047
Conversation
Seems instead of returning a unsuccessful answer it is better to throw a CloudRuntimeException for error handling.
Before it was possible that a Host was picked for the primary storage that was not even part of cluster, now we only consider hosts from either the same cluster or same zone depending on primary storage settings.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.20 #12047 +/- ##
============================================
- Coverage 16.18% 16.17% -0.01%
+ Complexity 13305 13299 -6
============================================
Files 5657 5657
Lines 498459 498465 +6
Branches 60492 60491 -1
============================================
- Hits 80694 80651 -43
- Misses 408783 408831 +48
- Partials 8982 8983 +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 |
|
@DaanHoogland 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 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 15718 |
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
Description
Before it was possible that a Host was picked for the primary storage
that was not even part of cluster, now we only consider hosts
from either the same cluster or same zone depending on primary storage
settings.
Also improve cleanup code on
copyAsyncoperations.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Hyperconverge and non hyperconverge Linstor cluster tested.
How did you try to break this feature and the system with this change?