support cloning host-based nfs volumes#467
Merged
Merged
Conversation
xuluna
previously approved these changes
Apr 17, 2025
Contributor
Merging this branch will not change overall coverage
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
xuluna
approved these changes
Apr 17, 2025
falfaroc
approved these changes
Apr 17, 2025
santhoshatdell
approved these changes
Apr 17, 2025
Contributor
Author
@santhoshatdell, yes it does. |
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
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.
Description
Requests to
CreateVolume()with another host-based NFS volume as the content source (a clone operation) would have a source volume ID containing the "nfs-" prefix. That volume ID would be passed to the driver for volume provisioning, and because the prefix is not parsed and removed, the driver will submit volume queries to the PowerStore API with volume UUIDs in the form of "nfs-" causing the requests to return errors, because of the malformed volume UUID.For host-based NFS volume clone operations, these changes will confirm the volume source is another host-based NFS volume by checking for and removing the "nfs-" prefix before submitting any requests to the PowerStore API.
GitHub Issues
List the GitHub issues impacted by this PR:
Checklist:
How Has This Been Tested?