Description of problem: the cluster-backup.sh script has a conflict to use the '/etc/kubernetes/static-pod-certs' folder if a custom API certificate is defined Version-Release number of selected component (if applicable): From the current GitHub repo, this issue seems to impact all current versions. How reproducible: Easily Steps to Reproduce: 1. Define a custom API certificate in the kube-apiserver config (oc edit apiserver cluste) 2. Wait for the certificate to be deployed. 3. Then running the `cluster-backup.sh` will fail as the folder **/etc/kubernetes/static-pod-certs** is already created. Actual results: the `etcdctl snapshot save` command failed with the error message: ~~~ Error: open /etc/kubernetes/static-pod-certs/secrets/etcd-all-certs/etcd-peer-<nodename>.crt: no such file or directory ~~~ Expected results: Backup to be successful. Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069