-
Notifications
You must be signed in to change notification settings - Fork 617
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
CSI node plugin fix for unstaging volumes #3178
Open
beornf
wants to merge
1
commit into
moby:master
Choose a base branch
from
beornf:node-plugin-unstage-volume
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
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 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'm not super-familiar with this code, but should this actually proceed if the volume was not found in
np.volumeMap
?i.e., the volume should be present if it was successfully staged. If a failure happened during staging, it wouldn't be added. Looking at
NodeStageVolume
further up;swarmkit/agent/csi/plugin/plugin.go
Lines 231 to 239 in e8ecf83
Perhaps this should be something like;
Or if it would be useful to have distinct errors for each situation
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.
Indeed the assumptions around state for unstaging would always hold true if
np.volumeMap
was made persistent:swarmkit/agent/csi/plugin/plugin.go
Lines 60 to 63 in ea1a7ce
I recall during testing it is possible that a volume had been staged before the node daemon restarted and
np.volumeMap
was empty. In the methodNodeUnpublishVolume
it always unpublishes the volume irrespective ofnp.volumeMap
.