🐞 bug: During the gs_pitr tool usability test, the error message is not clear and accurate, which cannot guide users to analyze and locate the fault.

Contents of your values.yaml file,if your helm deployment process goes wrong.
Contents of your CRD resource file. Include proxy.shardingsphere.apache.org/v1alpha1 and proxyconfig.shardingsphere.apache.org/v1alpha1
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version

Which phase is not functioning properly, is it the installation phase or the apply CRD phase ?
pitr tool (1) If enable_cbm_tracking is not set to on in OpenGauss, the error information reported by the backup front-end is not detailed and the error cause is not displayed. (2) If full backup is not performed and incremental backup is performed, the error information reported by the backup tool is not detailed and the error cause is not displayed. (3) Before the backup, the status of each shard OpenGauss node is abnormal. The error information reported by the backup tool is not detailed, and the error cause is not provided. (4) During gs_pitr backup on the server, the error message "error Create ss-proxy connect failed" is displayed no matter which parameter host, password, username, or port is incorrectly set. Check whether specific error information needs to be printed.

No response

apache / shardingsphere-on-cloud