fix(node): check for empty devicePath #344
Merged
Conversation
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
When the VolumeAttachment was created with v1.6.0 (or older) it has an empty publish context and we run into a cryptic error during mount. We should always check that the device path is set in the publish context. This will improve the error message for one of the bugs encountered in #278.
apricote
force-pushed
the
check-if-device-path-is-set
branch
from
99ad6e1 to
d09eb9b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When the VolumeAttachment was created with v1.6.0 (or older) it has an empty publish context and we run into a cryptic error during mount. We should always check that the device path is set in the publish context.
This will improve the error message for one of the bugs encountered in #278.
For details, see my comment: #278 (comment)