-
Notifications
You must be signed in to change notification settings - Fork 555
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
rbd: correct default encryption type (backport #5087) #5089
Conversation
Problem: When the encryptionType is not specified in the StorageClass, the default type (block) is used and stored in OMAP. However, during OMAP regeneration in a secondary cluster, the default type is incorrectly set to none. This discrepancy leads to errors during PVC cloning, with the message: `cannot create encrypted volume from unencrypted volume.` Solution: Update the default encryption type to consistently use block instead of none. Signed-off-by: Praveen M <[email protected]> (cherry picked from commit 0cfb2b0)
/test ci/centos/upgrade-tests-cephfs |
/test ci/centos/k8s-e2e-external-storage/1.29 |
/test ci/centos/upgrade-tests-rbd |
/test ci/centos/mini-e2e-helm/k8s-1.29 |
/test ci/centos/mini-e2e/k8s-1.29 |
/test ci/centos/k8s-e2e-external-storage/1.30 |
/test ci/centos/k8s-e2e-external-storage/1.31 |
/test ci/centos/mini-e2e-helm/k8s-1.30 |
/test ci/centos/mini-e2e-helm/k8s-1.31 |
/test ci/centos/mini-e2e/k8s-1.30 |
/test ci/centos/mini-e2e/k8s-1.31 |
Describe what this PR does
Problem: When the encryptionType is not specified in the StorageClass,
the default type (block) is used and stored in OMAP. However, during
OMAP regeneration in a secondary cluster, the default type is incorrectly
set to none. This discrepancy leads to errors during PVC cloning,
with the message:
cannot create encrypted volume from unencrypted volume.
Solution: Update the default encryption type to consistently use block
instead of none.
👇 Problem logs
In Secondary cluster -
encryptionType
parameter -csi.volume.encryptionType
is emptyFuture concerns
List items that are not part of the PR and do not impact it's
functionality, but are work items that can be taken up subsequently.
Checklist:
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>
: retest the<job-name>
after unrelatedfailure (please report the failure too!)
This is an automatic backport of pull request #5087 done by [Mergify](https://mergify.com).