Allow extend_volume even with storage_protocol mismatch #293
+7
−1
Conversation
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
…vstorageobject Change-Id: I02ac06dbe01d00cab739675b34cf600dea107360
Change-Id: I153545ed224fd1e26dd2bc4db25a516b61a2f9e1
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.
Allow extend_volume call, that would fail because of caps filter, due to storage_protocol mismatch between vmdk and vstorage object driver. We need this patch to allow volume_extend to work if the volume is not yet migrated to fcd
Change-Id: I02ac06dbe01d00cab739675b34cf600dea107360