CON 4206 - Volume gets cloned as wrong provisioning type - Bug Fix #482
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
abhishekb-hpe
requested review from
datamattsson,
dileepds,
pavansshanbhag,
raunakkumar,
rohit-balakrishna,
sijeesh and
suneeth51
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Bug Link - https://jira.storage.hpecorp.net/browse/CON-4206
Bug Description - Similarly, seen on PVC snapshot and restore when overriding the storage class to create a tpvv volume (originally storage class has "reduce" type) and when snapshot and restoring this PVC, the new cloned volume is created as reduce instead of tpvv.
Bug Fix- Added Code so as the PVC Created from shapshot always takes parent volume provisioning type only, also handed overrides such that if override is specified we remove the storageclass provisioning type and only consider PVC provisioning type to avoid conflict.
Earlier Screenshots
After Fixing Bug
