fix: Invalid "invalid encryption kms configuration" error (backport #3854) #3891
Conversation
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
this commit adds the validation for encryption value as false, and sets the type as none Signed-off-by: riya-singhal31 <rsinghal@redhat.com> (cherry picked from commit 38f5e86)
Signed-off-by: riya-singhal31 <rsinghal@redhat.com> (cherry picked from commit 347b4d2)
Signed-off-by: riya-singhal31 <rsinghal@redhat.com> (cherry picked from commit e92edd0)
Signed-off-by: riya-singhal31 <rsinghal@redhat.com> (cherry picked from commit b5e68c8)
mergify
bot
added
ok-to-test
|
/test ci/centos/k8s-e2e-external-storage/1.24 |
|
/test ci/centos/k8s-e2e-external-storage/1.25 |
|
/test ci/centos/k8s-e2e-external-storage/1.26 |
|
/test ci/centos/k8s-e2e-external-storage/1.27 |
|
/test ci/centos/mini-e2e-helm/k8s-1.24 |
|
/test ci/centos/mini-e2e-helm/k8s-1.25 |
|
/test ci/centos/mini-e2e-helm/k8s-1.26 |
|
/test ci/centos/mini-e2e-helm/k8s-1.27 |
|
/test ci/centos/mini-e2e/k8s-1.24 |
|
/test ci/centos/mini-e2e/k8s-1.25 |
|
/test ci/centos/mini-e2e/k8s-1.26 |
|
/test ci/centos/mini-e2e/k8s-1.27 |
|
/test ci/centos/upgrade-tests-cephfs |
|
/test ci/centos/upgrade-tests-rbd |
|
/retest ci/centos/mini-e2e/k8s-1.24 |
|
/retest ci/centos/upgrade-tests-cephfs |
|
/retest ci/centos/upgrade-tests-cephfs |
Failed while deploying rook: https://jenkins-ceph-csi.apps.ocp.cloud.ci.centos.org/blue/organizations/jenkins/upgrade-tests-cephfs/detail/upgrade-tests-cephfs/7194/pipeline/ |
|
/retest ci/centos/upgrade-tests-cephfs |
Creating a CephFS PVC failed, this PR only touches RBD? |
Yes, it passes now. |
This is an automatic backport of pull request #3854 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com