-
Notifications
You must be signed in to change notification settings - Fork 91
fix(drbd): prevent duplicate TCP ports after toggle-disk operations #476
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
Open
kvaps
wants to merge
3
commits into
LINBIT:master
Choose a base branch
from
kvaps:fix/drbd-duplicate-tcp-ports-after-toggle-disk
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I see how this is redundant with the call in
CtrlRscToggleDiskApiCallHandler line 1327. However here are my thoughts to this:If anything, it is the call in
CtrlRscToggleDiskApiCallHandlerline 1327 that is the redundant one, since theresetStoragePoolsmethod could technically be called from other places in the future. Removing it as you wanted would add the risk that this future new code/feature forgets to callensureStackDataExistswhich will leave a corrupt layer-tree within LINSTOR.That would mean that the line 1327 of
CtrlRscToggleDiskApiCallHandlercould be moved into the end of the then-case ofif (removeDisk)(i.e. currently between lines 1320 and 1321). However, with the same argument as before, adding some future new branch in thefinishOperationInTransactioncould also lead to forgetting to callensureStackDataExists.So here is what I'd rather suggest:
CtrlRscLayerDataFactoryto ensure that calling this method cannot be forgotten and instead just add a comment beforeCtrlRscToggleDiskApiCallHandlerline 1327 that we simply accept this redundancyensureStackDataExistsinCtrlRscLayerDataFactoryline 280 optional with something like this:And change the call in
CtrlRscToggleDiskApiCallHandlerline 1325 toctrlLayerStackHelper.resetStoragePools(rsc, false);The latter approach should prevent accidentally forgetting to call this in the future (worst case we add again a redundancy but never miss calling
ensureStackDataExistsentirely) but also gives the caller enough control to prevent redundancy.