-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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: Do not pretend handling disconnect paths that are non Linstor #8897
linstor: Do not pretend handling disconnect paths that are non Linstor #8897
Conversation
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, trusting provider specoific testing and will run regression suits
@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]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 9214 |
@blueorangutan test alma9 kvm-alma9 |
@DaanHoogland a [SL] Trillian-Jenkins test job (alma9 mgmt + kvm-alma9) has been kicked to run smoke tests |
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
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 tested.
I created a VM on a KVM enviroment; then, I sent a stop VM command:
- Without this patch, forced other adaptors to fail so that Linstor would run (using a debug tool), even not having Linstor in my environment,
disconnectPhysicalDisk
would return true. - After the patch, redid the same test, and the method returns false.
This testing is limited in a sense that I cannot test the case were Linstor should actually return true, but at least we shouldn't have any regressions for users that do not use Linstor.
[SF] Trillian test result (tid-9785)
|
@DaanHoogland From what I've looked at the errors from #8897 (comment), them look like an environment instability; could we run the CI once more just to be safe? |
@sureshanaparti @rohityadavcloud @shwstppr could we run the CI again? |
[SF] Trillian test result (tid-9795)
|
Rekicked CI by close/reopen. @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. |
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 9231 |
@JoaoJandre I had already started it in the background and it seems succeful:
sorry, for the lack of communication. |
Merging based on reviews, CI result and manual tests |
@DaanHoogland Who would merge this into 4.19 and main? |
@rp- , RMs do so on a regular basis. A lot of merge commits can be found. On any branche not in freeze you/any of us can as well. There is a tool git-fwd-merge in ./tools/git that can do it and rolls back on conflicts. when on the path it can be called as |
@rp- I merged a bunch forward including this. There was a conflict and I think I resolved it but you might want to check the method |
Looks fine for me |
Description
Excerpt PR from #8790, that only fixes Linstor adaptor pretending handling paths that don't belong to Linstor.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Manual with a Linstor cluster.
How did you try to break this feature and the system with this change?