Handle ReviveDBRestorePointNotFound error

vertica / vertica-kubernetes

Operator, container and Helm chart to deploy Vertica in Kubernetes

Apache License 2.0

44 stars 25 forks source link

Handle ReviveDBRestorePointNotFound error #675

Closed jizhuoyu closed 9 months ago

jizhuoyu commented 9 months ago

operator now handles ReviveDBRestorePointNotFound error returned from vclusterops
e2e test for invalid id and index
e2e test for cluster scaling before restoring

chinhtranvan commented 9 months ago

I don't have any comments in your PR. it looks good to me. e2e leg 6 was failed because it also has log rotation for editor.log I just fix the test in my PR. Perhaps, you can wait until my PR is merged.